Need to restart to see pushed images about harbor HOT 7 CLOSED

@AlexZeitler , thanks for your suggestion, I opened #59

from harbor.

i came across this issue, but i wait a moment, it will show the image. maybe something need update period.

from harbor.

There's a webhook in ui container to update the images in cache, it should not take more than a few seconds. @AlexZeitler, how long do you have to wait? Could you attach the config.yml of registry? It's location is harbor/Deploy/config/registry/config.yml

from harbor.

@reasonerjt I have been waiting for about 2 minutes.

config.yml:

version: 0.1
log:
  level: debug
  fields:
    service: registry
storage:
    cache:
        layerinfo: inmemory
    filesystem:
        rootdirectory: /storage
    maintenance:
        uploadpurging:
            enabled: false
http:
    addr: :5000
    secret: placeholder
    debug:
        addr: localhost:5001
auth:
  token:
    issuer: registry-token-issuer
    realm: http://localhost/service/token
    rootcertbundle: /etc/registry/root.crt
    service: token-service

notifications:
  endpoints:
      - name: harbor
        disabled: false
        url: http://localhost/service/notifications
        timeout: 500
        threshold: 5
        backoff: 1000

from harbor.

@AlexZeitler I see, in harbor.cfg you need to set the hostname with the IP of eth0 such as "192.168.0.2", not "localhost".
See the section of notifications, the registry will make http call to the "url", and since registry is running in a container and the /service/notofications/ is running in another process outside the container, the call will fail and the cache will not be updated.

from harbor.

@reasonerjt Thanks, this did the trick! 👍

Just for the understanding: ui (which hosts /service/notifications) and registry both run in containers and they're linked according to docker-compose.yml (at least ui can see registry).

So if registry would also link ui it could access it by its IP which is exposed as an environment variable to the registry container.

Or if you switch to docker-compose 1.6+ you could just use the default network and access the containers by their names so http://ui/service/notifications should just work without even setting host or IP.

Is there a reason for not doing that? (sorry, I'm just beginning with golang...)

from harbor.

Closing this issue and the problem is fixed. further work will be tracked in #59

from harbor.