That’s it! We made docker-compose access private repositories in different registries. Login_other-registry_1 exited with code 0 Only then can we start all services with docker-compose:Ĭreating network "login_default" with the default driver $ docker login some-other-docker-registry.io That way our credentials will be stored in our machine: $ docker login We should be logged in to both registries before using docker-compose for the first time. The third image is stored in a private repository on a different registry. The first is a public image, and the second is private. The first two services reference images in the default Docker registry. It’s an official image that only prints how to get started with Docker and finishes right after. We used the hello-world image to simplify our example. ![]() ![]() Image: some-other-docker-registry.io/myuser/hello-world In this case, our docker-compose.yml file might begin: version: '3' Let’s say we need to work with different registries and levels of access.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |