Unregistry
Dev tools
container deployment
SHOW HN2025
726points
164comments
#38of 3,837 in 2025
Top 1%of 2025 by points
How HN took it
CuriousMostly questions and neutral comments
30 positive, 47 neutral or asking, 1 mixed, 7 critical, out of 85 comments about the project. Thread score +0.37.
Idea: 22 for, 4 againstDesign: 1 for, 3 againstPerformance: 4 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Idea seen as long overdue and elegant, with the pussh pun praised
From 4 comments
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…
nine_k on HNAmazing. Our company has to push gigantic docker images to IoT style devices, and we’ve had to maintain an installer script that downloads and stands up a local dummy registry,…
sebastos on HNThis should have always been a thing! Brilliant. Docker registries have their place but are overall over-engineered and an antithesis to the hacker mentality.
metadat on HNI think this is great and have long wondered why it wasn’t an out of the box feature in Docker itself.
rcarmo on HN
Useful for avoiding registry costs and transferring only missing layers
From 3 comments
This is excellent. I've been doing the save/load and it works fine for me, but I like the idea that this only transfers missing layers. FWIW I've been saving then using mscp to…
actinium226 on HNI think it will be a good fit for me. Currently our 3GB docker image takes a lot of time to push to Github package registry from Github Action and pull from EC2.
iw7tdb2kqo9 on HNI'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…
layoric on HN
Objections
Requires running an unregistry container on the remote host
From 1 comment
Amazing. Our company has to push gigantic docker images to IoT style devices, and we’ve had to maintain an installer script that downloads and stands up a local dummy registry,…
sebastos on HN
Couples deployment to a service, making scaling and blue/green harder
From 1 comment
Neat 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…
fellatio on HN
Requests
Support for Kubernetes image pulls
From 2 comments
THANK you. Can you do the same for kubernetes somehow?
spwa4 on HNDoes this work with Kubernetes image pulls?
czhu12 on HN
Docker compose support
From 1 comment
This is really cool. Do you support or plan to support docker compose?
koakuma-chan on HN
Integration into Docker/Podman natively
From 1 comment
very cool. now lets integrate this such that we can do `docker/podman push localimage:localtag ssh://hostname:port/remoteimage:remotetag` without extra software installed :)
s1mplicissimus on HN
Questions
How does it differ from skopeo or docker save/load
From 3 comments
What’s the difference between this and skopeo? Is it the ssh support ? I’m not super familiar with skopeo forgive my ignorance https://github.com/containers/skopeo
nothrabannosir on HNWhat 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?
yjftsjthsd-h on HNA 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)!
jlhawn on HN
Does it work with buildah or OCI tooling without full Docker
From 1 comment
This 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…
alisonatwork on HN
Alternatives named
docker save piped to docker load over SSH
From 3 comments
A 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)!
jlhawn on HNI always just use "docker save" to generate a TAR file, then copy the TAR file to the server, and then run "docker load" (on the server) to install the TAR file on the target…
quantadev on HNNice to only have to push the layers that changed. For me it's been enough to just do "docker save my-image | ssh host 'docker load'" but I don't push images very often so for me…
larsnystrom on HN
Docker contexts / DOCKER_HOST over SSH
From 3 comments
Is this different from using a remote docker context? My workflow in my homelab is to create a remote docker context like this... (from my local development machine) > docker…
revicon on HNI've been very happy doing this: DOCKER_HOST=“ssh://user@remotehost” docker-compose up -d It works with plain docker, too. Another user is getting at the same idea when they…
jdsleppy on HNHow about using docker context. I use that a lot and works nicely.
armx40 on HN
skopeo
From 1 comment
What’s the difference between this and skopeo? Is it the ssh support ? I’m not super familiar with skopeo forgive my ignorance https://github.com/containers/skopeo
nothrabannosir on HN
docker-pushmi-pullyu
From 1 comment
Functionality-wise this is a lot like docker-pushmi-pullyu[1] (which I wrote), except docker-pushmi-pullyu is a single relatively-simple shell script, and uses the official…
matt_kantor on HN
Spegel
From 1 comment
Not a torrent protocol but p2p, check out https://github.com/spegel-org/spegel it's super cool. I took inspiration from spegel but built a more focused solution to make a…
psviderski on HN
Self-hosted registry such as Zot
From 1 comment
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…
scott113341 on HN