-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Description
I'm getting the below issue when trying to update my images from a private repository. I've provided the config.json to authenticate against my repository. I'm running https://hub.docker.com/_/registry/ as my registry. Any idea why this might be happening?
user@server:~$ docker run -d --name watchtower -v /home/user/.docker/config.json:/config.json -v /var/run/docker.sock:/var/run/docker.sock centurylink/watchtower --debug
3c0c984b54da2e3d02743a473f8bae7ca21196f4c8efef5c1d6189b33da4e872
user@server:~$ docker logs watchtower
time="2017-01-17T19:40:05Z" level=debug msg="Retrieving running containers"
time="2017-01-17T19:40:05Z" level=info msg="Checking containers for updated images"
time="2017-01-17T19:40:05Z" level=debug msg="Retrieving running containers"
time="2017-01-17T19:40:05Z" level=debug msg="Pulling centurylink/watchtower:latest for /watchtower"
time="2017-01-17T19:40:06Z" level=debug msg="Pulling privateregistry:443/my-image for /project_web_1"
Error: image my-image not found
Docker pull works on my local machine using the same credentials. My registry uses a self signed certificate, so I had to add a ca.crt to /etc/ssl/certs.d/privateregistry:443/ca.crt. Do I need to mount this in the watchtower container as well?
Metadata
Metadata
Assignees
Labels
No labels