Publish it to the main docker registry? about docker-gitlab-mirrors HOT 3 CLOSED

I could publish the container in docker hub as well, but I prefer quay.io
since they provide automated container builds.

Is there a reason that you need it published on the official registry or is
it just a matter of preference?

On Mon, Jun 20, 2016, 11:32 AM Michel Samia [email protected]
wrote:

Hi,

I noticed that most projects put their container images to the cetral
docker registry so in docker-compose.yml you put something like

gitlabmirror:
image: klowner/gitlab-mirrors:latest

instead of:

gitlabmirror:
image: quay.io/klowner/gitlab-mirrors:latest

I'm relatively new to docker, so maybe this request doesn't make sense...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2, or mute the
thread
https://github.com/notifications/unsubscribe/AAAknsRRIwiqd0DPIcJliEHeVtHTImReks5qNsCMgaJpZM4I54iV
.

from docker-gitlab-mirrors.

It was more a question than a bug report to find out what is the difference between these two ways. You can close it :)

from docker-gitlab-mirrors.

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 hostname/namespace/name pattern then you can docker push and docker pull to the corresponding registry. For example, if you decided to run your own registry at docker.example.com you would tag your images with docker.example.com/startdust85/docker-gitlab-mirrors:latest and then when you docker push that it'll go to that registry server.

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 Dockerfile in your repository and then serve the resulting image.

from docker-gitlab-mirrors.