Nice. 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.
and prone to collision!
Show HN: Unregistry – “docker push” directly to servers without a registry
41–50 of 178 posts
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#42This is a cool idea that seems like it would integrate well with systems already using push deploy tooling like Ansible. It also seems like it would work as a good hotfix deployment mechanism at companies where the Docker registry doesn't have 24/7 support.
Does it integrate cleanly with OCI tooling like buildah etc, or if you need to have a full-blown Docker install on both ends? I haven't dug deeply into this yet because it's related to some upcoming work, but it seems like bootstrapping a mini registry on the remote server is the missing piece for skopeo to be able to work for this kind of setup.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#43It's very silly that Docker didn't work this way to start with. Thank you, it looks cool!
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#44Does 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.
`ssh -R` and `ssh -L` are amazing, and I just learned that -L and -R both support unix sockets on either end and also unix socket to tcp socket https://manpages.ubuntu.com/manpages/noble/man1/ssh.1.html#:...
I would presume it's something akin to $(ssh -L /var/run/docker.sock:/tmp/d.sock sh -c 'docker -H unix:///tmp/d.sock save | docker load') type deal
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#45Neat idea. This probably has the disadvantage of coupling deployment to a service. For example how do you scale up or red/green (you'd need the thing that does this to be aware of the push).
Edit: that thing exists it is uncloud. Just found out!
That said it's a tradeoff. If you are small, have one Hetzner VM and are happy with simplicity (and don't mind building images locally) it is great.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#46A 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)!
On podman this is built in as native command podman-image-scp[0], which perhaps could be more efficient with SSH compression.
[0] https://docs.podman.io/en/stable/markdown/podman-image-scp.1...
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#47It's very silly that Docker didn't work this way to start with. Thank you, it looks cool!
You can already achieve the same thing by making your image into an archive, pushing it to your server, and then running it from the archive on your server.
Saving as archive looks like this: `docker save -o may-app.tar my-app:latest`
And loading it looks like this: `docker load -i /path/to/my-app.tar`
Using a tool like ansible, you can achieve easily what "Unregistry" is doing automatically. According to the github repo, save/load has the drawback of tranfering the whole image over the network, which could be an issue that's true. And managing the images instead of archive files seems more convenient.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#48This is a cool idea that seems like it would integrate well with systems already using push deploy tooling like Ansible. It also seems like it would work as a good hotfix deployment mechanism at companies where the Docker registry doesn't have 24/7 support. Does it integrate cleanly with OCI tooling like buildah etc, or if you need to have a full-blown Docker install on both ends? I haven't dug deeply into this yet b…
It needs docker daemon on both ends. This is just a clever way to share layer between two daemons via ssh.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#49Nice. 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.
and prone to collision!
Indeed so! Because it's art, not engineering. The engineering approach would require a recognizably distinct command, eliminating the possibility of such a pun.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#50I’ve wanted unregistry for a long time, thanks so much for the awesome work!