4 ms·

I feel like the main response should be "OK, we'll just host our own Docker Registry." This has been available as a docker image since the very beginning, whic

I feel like the main response should be "OK, we'll just host our own Docker Registry." This has been available as a docker image since the very beginning, which might not be good enough for everyone, but I think it will work for me and mine.

geerlingguy 6y ago
Note that for OSS images, that's a non-trivial thing to do—you have to have somewhere to run the image, and somewhere to store your images (e.g. S3), both of which are non-free, and would also require more documentation and less discoverability than Docker Hub offers.
- laurencerowe 6y ago
  GitHub Packages is free for public repositories so seems like a good option for OSS which likely have a GitHub presence already. https://github.com/features/packages https://github.com/features/packages
  - GordonS 6y ago
    Huh, I knew GitHub Packages supported npm, NuGet and Maven, but had no idea it supported Docker images too. My guess is a lot of people don't know this. If it becomes better known, I can imagine something of an exodus from Docker Hub to GitHub Packages for OSS projects.
    - laurencerowe 6y ago
      Further down someone mentioned that it still requires logging in to download public packages, though they're apparently working on it.
    - ithkuil 6y ago
      Currently github docker registry is missing some important features, such as arbitrary media types (useful for hosting helm charts and similar things)
  - grafelic 6y ago
    Github Packages Registry does not support pulling by digest, making it unusable for k8s/OpenShift. https://github.community/t/cannot-pull-docker-image-from-github-package-registry-by-digest/14342/12 https://github.community/t/cannot-pull-docker-image-from-git...
- rumanator 6y ago
  Last time I checked, GitLab offered a free Docker container registry for all projects.
Legogris 6y ago
Agreed that self-hosting registries should be way more common than it is today and maybe even standard practice. It's crazy easy to do; just start the registry container with a mapped volume and you're done. Securing, adding auth/auth and properly configuring your registry for exposure to the public internet, though... The configuration for that is very poorly documented IMO. EDIT: Glancing through the docs, they do seem to have improved on making this more approachable relatively recently. https://docs.docker.com/registry/deploying/ https://docs.docker.com/registry/deploying/

geerlingguy 6y ago

Note that for OSS images, that's a non-trivial thing to do—you have to have somewhere to run the image, and somewhere to store your images (e.g. S3), both of which are non-free, and would also require more documentation and less discoverability than Docker Hub offers.

laurencerowe 6y ago
GitHub Packages is free for public repositories so seems like a good option for OSS which likely have a GitHub presence already. https://github.com/features/packages https://github.com/features/packages
- GordonS 6y ago
  Huh, I knew GitHub Packages supported npm, NuGet and Maven, but had no idea it supported Docker images too. My guess is a lot of people don't know this. If it becomes better known, I can imagine something of an exodus from Docker Hub to GitHub Packages for OSS projects.
  - laurencerowe 6y ago
    Further down someone mentioned that it still requires logging in to download public packages, though they're apparently working on it.
  - ithkuil 6y ago
    Currently github docker registry is missing some important features, such as arbitrary media types (useful for hosting helm charts and similar things)
- grafelic 6y ago
  Github Packages Registry does not support pulling by digest, making it unusable for k8s/OpenShift. https://github.community/t/cannot-pull-docker-image-from-github-package-registry-by-digest/14342/12 https://github.community/t/cannot-pull-docker-image-from-git...
rumanator 6y ago
Last time I checked, GitLab offered a free Docker container registry for all projects.

Legogris 6y ago

Agreed that self-hosting registries should be way more common than it is today and maybe even standard practice. It's crazy easy to do; just start the registry container with a mapped volume and you're done. Securing, adding auth/auth and properly configuring your registry for exposure to the public internet, though... The configuration for that is very poorly documented IMO. EDIT: Glancing through the docs, they do seem to have improved on making this more approachable relatively recently. https://docs.docker.com/registry/deploying/ https://docs.docker.com/registry/deploying/