I have a Dockerfile
which is going to be implemented FROM
a private registry's image. I build this file without any problem with Docker version 1.12.6, build 78d1802
and docker-compose version 1.8.0, build unknown
, but in another machine which has Docker version 17.06.1-ce, build 874a737
and docker-compose version 1.16.1, build 6d1ac21
, the docker-compose build
returns:
FROM my.private.gitlab.registry:port/image:tag http://my.private.gitlab.registry:port/v2/docker/image/manifests/tag: denied: access forbidden
docker pull my.private.gitlab.registry:port/image:tag
returns the same.
Notice that I tried to get my.private.registry:port/image:tag
and http://my.private.registry:port/v2/docker/image/manifests/tag
has been catched.
If this is an authenticated registry, then you need to run docker login <registryurl>
on the machine where you are building this.
This only needs to be done once per host. The command then caches the auth in a file
$ cat ~/.docker/config.json { "auths": { "https://index.docker.io/v1/": { "auth": "......=" } } }
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With