chartmuseum VS hub-feedback

We may switch over to Chartmusuem, and something like Charts-Syncer to try to help with this, or maybe abandon the whole idea of mirroring external repositories and just keep our repository hosting internal projects. What are your thoughts on this?

Also trying to find a small self-hosted container registry (not some beast like goharbor.io) and possibly a Helm chart repository (looking into chartmuseum.com). Anyone got some recommendations?

ChartMuseum is indeed open source and is on GitHub.

This is also basically an s3 proxy, but it specifically implements the Terraform Registry API so that things like version constraints are handled correctly. If you use Helm at all, an analogous project for charts would be https://github.com/helm/chartmuseum

Another benefit of Helm is in it's package management. If your application requires another team's application up and running, they can publish their Helm chart to a remote repository like a ChartMuseum. You can then install their application into your Kubernetes by naming that remote chart combined with a local values file. E.g., helm install other-teams-app https://charts.mycompany.com/other-teams-app-1.2.3.tgz -f values-other-teams-app.yaml. This is convenient because it means you don't have to checkout their project and dig through it for their helm charts to get up and running - all you need to supply is your own values file.

Docker (and Docker Hub) have the worst fucking maintainers.

We can pull the open-source docker images also. To use this we have to create an account in the docker hub.

To transfer the image between your local machine and the server, you'll need a registry such as Docker Hub or GitHub Container Registry. (Technically you can compress images and distribute them as files but it's more of a headache than it's worth) There are plenty of registries that will allow you to host private images if that's a concern for you, but it will be harder to find a free/cheap solution. You can also host your own registry using the Distribution Project. But be warned that while hosting a basic registry is really easy, locking it down can be a pain because of the lack of well maintained and easy to use projects.

Ideally you run your the build step on CI and push the built image into container registry (like dockerhub or ghcr). You can then download the image on server and run it. You can do this with docker-compose as well, just use the image instead of dockerfile to define your web app like you do with proxy and DB.

Registry services such as GitHub Container Registry, Docker Hub, or, AWS ECR are ubiquitous, and many people are already using them as part of their workflow deploying cloud native applications.

The world has built an ecosystem around Docker-compatible images and APIs, which is a problem given Docker itself is proprietary software with a really aggressive commercial use license. Even just FOSS image hosting is in peril now, which is all about the terms and not the code, and even a rewrite can't fix that problem.

For this article, we will use Nginx, one of the most resilient and stable images. Let’s go over to Docker hub and download our image.

A free Docker Hub account. We will be using DockerHub as our container registry to push our image.