Question
How to docker push to DigitalOcean private container registry for a Remote User
- Posted on October 5, 2020
- ContainerDockerDigitalOcean API and CLI (doctl)
Asked by favas
I have successfully setup the private Docker registry with authentication. However this authentication is only for docker pull command. Doing a docker push command gives me
denied: requested access to the resource is denied
unauthorized: authentication required
I understand the concept of doctl registry login and pushing from my end as admin user. How can i do the same for a remote user without giving the remote user read and write API access token from DO control panel.
by generating and sharing doctl registry docker-config ( from my end) he was able to pull from the DO private registry but push failed with the above msg
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Docker Registry is an application that manages storing and delivering Docker container images. Docker images guarantee consistent runtime environment through virtualization, but building an image can take time— registries centralize container images and reduce build times.In this tutorial, you’ll set up and secure your own private Docker Registry using Docker Compose and Nginx. Then, you’ll be able to push custom Docker images to your private registry and pull the image securely from a remote server. Choose your operating system to get started.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hi there @favas,
I believe that you need to make sure that your image is tagged with fully qualified destination path:
After that, when pushing the image again you need to use the following syntax:
Let me know how it goes! Regards, Bobby