Ripe probe & Docker

Очередной обновление RIPE Atlas Docker Image (с 5080 до 5100) принесло пару неприятных сюрпризов.

Для начала поменялся docker-compose.yml для запуска:

services:
  ripe-atlas:
    container_name: ripe-atlas.loc
    hostname: ripe-atlas.loc
    image: docker.io/jamesits/ripe-atlas:latest
    restart: always
    environment:
      RXTXRPT: "yes"
    volumes:
      - ripe-atlas:/etc/ripe-atlas
      - ripe-atlas:/run/ripe-atlas
      - ripe-atlas:/var/spool/ripe-atlas
    cap_drop:
      - ALL
    cap_add:
      - NET_RAW
      # required for tini
      - KILL
      # required for `setpriv` to work
      - SETUID
      - SETGID
      # required for the entrypoint script to auto-fix the permissions of the directories
      - CHOWN
      - FOWNER
      - DAC_OVERRIDE
    mem_limit: "64000000000"
    mem_reservation: 64m
    logging:
      driver: json-file
      options:
         max-size: 10m
    network_mode: bridge

volumes:
  ripe-atlas:
    driver: local

Поменялись права и директории для хранения:

Upgrading from 5080 to 5100 or Later:

At version 5090, upstream introduced a lot changes that require manual intervention.

You need to update the container startup arguments. See Running for an example. Note that new permissions are required to make the directory initialization process work.

The SSH keys are stored at /etc/ripe-atlas now. Please mv /var/atlas-probe/etc /etc/ripe-atlas and make sure they are owned by 101:999 (before subuid/subgid mapping, if applicable).

/var/atlas-probe is not used anymore and should be removed.

/var/spool/ripe-atlas and /run/ripe-atlas are now used to store probe runtime info.

If you are still using latest-{arch} tags, please update to use only latest.

(с) https://github.com/Jamesits/docker-ripe-atlas

И даже если все сделать по правильному — у меня зонд не завелся.
Пришлось ставить пустую инсталляцию и регистрировать заново public key.