Neat project and approach! I got fed up with expensive registries and ended up self-hosting Zot [1], but this seems way easier for some use cases. Does anyone else wish there was an easy-to-configure, cheap & usage-based, private registry service?
Show HN: Unregistry – “docker push” directly to servers without a registry
31–40 of 178 posts
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#32A quick and dirty version: docker -H host1 image save IMAGE | docker -H host2 image load note: this isn't efficient at all (no compression or layer caching)!
That method is actually mentioned in their README:
> Save/Load - `docker save | ssh | docker load` transfers the entire image, even if 90% already exists on the server
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#33Does it start a unregistry container on the remote/receiving end or the local/sending end? I think that runs remotely. I wonder if you could go the other way instead?
You mean ssh'ing into the remote server, then pulling image from local? That would require your local host to be accessible from the remote host, or setting up some kind of ssh tunneling.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#34Love it!
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#35[dead]
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#36A quick and dirty version: docker -H host1 image save IMAGE | docker -H host2 image load note: this isn't efficient at all (no compression or layer caching)!
[deleted]
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#37[deleted]
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#38What is the container for / what does this do that `docker save some:img | ssh wherever docker load` doesn't? More efficient handling of layers or something?
Yeah exactly, which is crucial for large images if you change only a few last layers.
The unregistry container provides a standard registry API you can pull images from as well. This could be useful in a cluster environment where you upload an image over ssh to one node and then pull it from there to other nodes.
This is what I’m planning to implement for Uncloud. Unregistry is so lightweight so we can embed it in every machine daemon. This will allow machines in the cluster to pull images from each other.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#39Nice. And the `pussh` command definitely deserves the distinction of one of the most elegant puns: easy to remember, self-explanatory, and just one letter away from its sister standard command.
It's fine, but it wouldn't hurt to have a more formal alias like `docker push-over-ssh`.
EDIT: why I think it's important because on automations that are developed collaboratively, "pussh" could be seen as a typo by someone unfamiliar with the feature and cause unnecessary confusion, whereas "push-over-ssh" is clearly deliberate. Think of them maybe as short-hand/full flags.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#40I'm so glad there are tools like this and swing back to selfhosted solutions, especially leveraging SSH tooling. Well done and thanks for sharing, will definitely be giving it a spin.