• This site is a private, non-commercial website. As such, you're welcome here as long as you were invited. If you would like an invite, reach out to Cliff Spark

Show HN: Unregistry – “docker push” directly to servers without a registry

  • Thread starter Thread starter psviderski
  • Start date Start date
P

psviderski

I got tired of the push-to-registry/pull-from-registry dance every time I needed to deploy a Docker image.
In certain cases, using a full-fledged external (or even local) registry is annoying overhead. And if you think about it, there's already a form of registry present on any of your Docker-enabled hosts — the Docker's own image storage.
So I built Unregistry [1] that exposes Docker's (containerd) image storage through a standard registry API. It adds a docker pussh command that pushes images directly to remote Docker daemons over SSH. It transfers only the missing layers, making it fast and efficient.

Code: 
  docker pussh myapp:latest user@server
Under the hood, it starts a temporary unregistry container on the remote host, pushes to it through an SSH tunnel, and cleans up when done.
I've built it as a byproduct while working on Uncloud [2], a tool for deploying containers across a network of Docker hosts, and figured it'd be useful as a standalone project.
Would love to hear your thoughts and use cases!
[1]: GitHub - psviderski/unregistry: Push docker images directly to remote servers without an external registry
[2]: GitHub - psviderski/uncloud: A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨


Comments URL: Show HN: Unregistry – “docker push” directly to servers without a registry | Hacker News

Points: 243

# Comments: 59

Continue reading...
 
Back
Top