one-click-apps VS registry.k8s.io

There are images for it on Docker Hub. I wrote a Redmine deployment spec for the PaaS I use (Caprover) for my personal app server. It’s a lot like Docker Compose, but as it actually functions using the Docker API, some Compose features are unavailable. If you’re familiar with Compose, you should be able to easily adapt this Caprover template: https://github.com/caprover/one-click-apps/blob/aaa12a4f37f7...

https://github.com/caprover/caprover https://github.com/caprover/one-click-apps

> Which One-Click App are you using? I looked over their list, but couldn't find the Docker Registry. Thanks!

I'm not sure about them, but Nexus might fit the bill from that list: https://github.com/caprover/one-click-apps/blob/master/publi...

It's what I'm using for myself (though with just Docker Swarm + Apache2, without Caprover) and has worked well for years.

Note that mattermost by default phones home to a spyware analytics service even when you selfhost it. The env vars for disabling it are hidden/undocumented.

Copy the diagnostics/securityalert env vars from here, as well as the sed lines:

https://github.com/caprover/one-click-apps/blob/master/publi...

If you stop to think about, what AWS is selling here, it's quite funny. Most of the infrastructure behind registry.k8s.io is hosted on AWS (and also GCP). So AWS essentially tells you: Don't trust the upstream registry, it might go down, cache it on your own registry, hosted also by us.

For example: if you only allow cluster autoscaler and metrics server from registry.k8s.io you can pull those images through the cache as someone who has create repo IAM privileges. If someone without create repo privileges tries to pull a new image it will fail because they can't create the initial repo.

https://registry.k8s.io (the root url at /) redirects you to https://github.com/kubernetes/registry.k8s.io where we have an issue tracker.

❗ This container is having trouble accessing https://registry.k8s.io

Hosting a forwarding / redirect server instead of actually hosting images is probably a decent idea.

The K8s proxy is redirecting from only hosting on GCR to community-owned registries - https://kubernetes.io/blog/2023/03/10/image-registry-redirec...

You can view the code here - https://github.com/kubernetes/registry.k8s.io

But because everyone is already pointing at gcr.io (just like many openfaas users point at docker.io/) - they're having to do a huge campaign to announce the new URL - the same would apply with the author's solution here.

I wrote some automation for hosting (not redirects) in arkade with the OSS registry - Get a TLS-enabled Docker registry in 5 minutes - https://blog.alexellis.io/get-a-tls-enabled-docker-registry-...

The registry is also something you can run on a VM if you so wish, and have act as a pull through cache.

Apart from reliability - GitHub's container registry is the current next best option - but we have to ask ourselves, what happens when they start charging or the outages start to last longer or are more frequent than 1-2 times per week as we've seen in Q1 2023.

One annoyance with how docker images are specified is they include the location where they are stored. So if you want to change where you store you image you break everyone.

I wonder if what regsitry.k8s.io does could be generalized:

https://github.com/kubernetes/registry.k8s.io/blob/main/cmd/...

The idea is the depending on which cloud you are pulling the image from, they will use the closest blob store to service the request. This also has the effect that you could change the source of truth for the registry without breaking all Dockerfiles.

If you are using updated helm charts then most of them have already replaced with registry.k8s.io, for example nginx ingress so not really breaking change.