Docker Community Forums

Share and learn in the Docker community.

Unsupported config option for services.registery: 'notifications'


(Oshani) #1

Hi All,

I am trying to set up a portus site, and I can’t get the registry notifications to work. In fact, I can’t setup the notifications option at all.

This is what I have in the compose file:

  registry:
    image: "registry:2"
    container_name: registery
    notifications:
      endpoints:
        - name: portus
          url: http://docker01.iucc.ac.il:8833/v2/webhooks/events
          timeout: 500ms
          threshold: 5
          backoff: 1s
    volumes:
      - /opt/docker/registry/registry:/var/lib/registry
    ports:
      - 5000:5000
    restart: always

But docker-compose says that the notifications options is not valid:

root@cobuntu:/opt/docker/portus# docker-compose create
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.registery: 'notifications'

I am using Ubuntu 16.04 and:

oshani@docker01:/opt/docker/portus$ docker -v
Docker version 17.05.0-ce, build 89658be
oshani@docker01:/opt/docker/portus$ docker-compose -v
docker-compose version 1.14.0, build c7bdf9e

I also tried installing on Ubuntu 18.04 but got the same problem.

Please help!

Many thanks,

Oren Shani


(Martin Terp) #2

Hi :slight_smile:

Its because its not a docker-compose configuration, its a registry configuration.
What i would do, is to copy out the running config of registry, add the notification part and mount the config file like described here, under “Overriding the entire configuration file”


(Oshani) #3

Hi Martin,

Thank you for clarifying that. I was able to add the notification option into the registry config file and now it seems to work. I can see the events going from the registry into portus and even written into the portus db, however nothing appears in the GUI ( neither the image I pushed, nor the activities ).

I saw in the docs that the time between the registry and the portus containers must be in sync, well in my case the time is in sync the timezone definition differs. Could this still be the problem?

Thanks

Oren