The registry and registry-frontend are the container names in my stack. Let's briefly break this down, as its just plain configuration (without password, S3 or SSL). Here's the docker-compose.yml file we start with:Įnter fullscreen mode Exit fullscreen mode We can use docker-compose to run the app stack, instead of running each container separatley. An app stack is a group of apps (stack) that is linked together to perform certain tasks. Each one of the components runs inside its own container, which forms the app stack. It has a front-end component (which is optional) that allows you to access the registry data from a browser. The registry app itself runs in a container. For the rest of this post, I assume you read the Registry Overview and Understanding Docker Registry at the official site.
#How to curl auth with docker ip how to
I'll explain how to implement the three items mentioned above. In this post, I address the issues I had encountered when I deployed our registry server. You should read it to get a grasp of what is it and how to run it. The official Docker documentation covers the subject in-depth. "The Registry is a stateless, highly scalable server side application that stores and lets you distribute Docker images."
0 kommentar(er)
