Hacker Newsnew | past | comments | ask | show | jobs | submit | VadimBauer's commentslogin

Good wrightup


Many people are quite upset. But on the other hand, how many years could this work? Petabytes of data and traffic.

When we started to offer an alternative to Docker Hub in 2015-2016 with container-registry.com, everyone was laughing at us. Why are you doing that, you are the only one, Docker Hub is free or almost free.

Owning your data and having full control over the distribution is crucial for every project, event open source.


Many people are quite upset. But on the other hand, how many years could this work? Petabytes of data and traffic.

When we started to offer an alternative to Docker Hub in 2015-2016 with container-registry.com, everyone was laughing at us. Why are you doing that, you are the only one, Docker Hub is free or almost free.

Owning your data and having full control over the distribution is crucial for every project, event open source.


you can use https://container-registry.com/ to store your images instead of Docker Hub.


Please be clear about your affiliation with this service (as you were in another thread). Anyway, looks it might be useful with Docker shooting themselves in the foot.


We run a CNCF Harbor-based container registry service (https://container-registry.com/), happy to help the project and offer a registry free of charge. Harbor has the valuable option that allows you to replicate images to other registries. So, you push images to a central place and from there they are automatically replicated to ghcr, gcr, ecr, Docker Hub and so on.

Happy to show and explain the various options and possibilities to the community here.


thx, also switched now to nip.io as well.


There a few valid situations where you don’t want to follow the common deployment practice by pushing to container registry and then let Kubernetes pull it during deployment.

This is mostly the case during the software development phase where you quickly want to test your code on Kubernetes cluster local or remote, because the whole container image up and download is slow.

> A key feature of BuildKit CLI for kubectl is that it strives to make the images you build immediately available in the container runtime of your Kubernetes cluster so you can “bounce” your pod(s) to pick up a freshly built image with virtually no overhead.


Smart things, like smart plugs, bulbs, locks or everything that is remotely controllable and manageable via App or Cloud.

It is not regulated what happens in the case that the vendor isn't able or willing to support those devices anymore. Keeping Apps up to date and new apps if new Mobile OSes arise or keep the light on in general. Right now it all depends on the goodwill of the vendor.

If the provider decides to not support anymore for whatever reason you have a smart brick!


This re-launch covers everything from the homepage, to listing end-users, sponsors, contributors (randomly chosen) and the blog has also had a make-over.


Thanks for sharing :-)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: