-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish it to the main docker registry? #2
Comments
I could publish the container in docker hub as well, but I prefer quay.io Is there a reason that you need it published on the official registry or is On Mon, Jun 20, 2016, 11:32 AM Michel Samia notifications@github.com
|
It was more a question than a bug report to find out what is the difference between these two ways. You can close it :) |
Oh, no worries. They're largely the same, they're both docker registry servers. The official registry has no bells or whistles like some of the others such as quay.io. You can tag a container with just about any string, but if you use the Quay.io is cool because you can set it up so if you push to a Github repository, Quay will start an automated build of the |
Hi,
I noticed that most projects put their container images to the cetral docker registry so in docker-compose.yml you put something like
instead of:
I'm relatively new to docker, so maybe this request doesn't make sense...
The text was updated successfully, but these errors were encountered: