I've been using ttl.sh for a long time, but only for public, temporary code. This is a really cool idea!
Wow ttl.sh is a really neat idea, thank you for sharing!
Show HN: Unregistry – “docker push” directly to servers without a registry
81–90 of 178 posts
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#82This is super slick. I really wish there was something that did the same, but using torrent protocol, so all your servers shared it.
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 registry out of a Docker/containerd daemon. A lot of other cool stuff and workflows can be built on top of it.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#83this is useful. thanks for sharing
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#84Does 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?
It starts an unregistry container on the remote side. I wonder, what's the use case on your mind for doing it the other way around?
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#85Takes a look at pipeline that builds image in gitlab, pushes to artifactory, triggers deployment that pulls from artifactory and pushes to AWS ECR, then updates deployment template in EKS which pulls from ECR to node and boots pod container.
I need this in my life.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#86Takes a look at pipeline that builds image in gitlab, pushes to artifactory, triggers deployment that pulls from artifactory and pushes to AWS ECR, then updates deployment template in EKS which pulls from ECR to node and boots pod container. I need this in my life.
My last projects pipeline spent more time pulling and pushing containers than it did actually building the app. All of that was dwarfed by the health check waiting period, when we knew in less than a second from startup if we were actually healthy or not.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#87Sweet. I been wanting this for long.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#88Considering the nature of servers, security boundaries and hardening, > Linux via Homebrew Please don't encourage this on Linux. It happens to offer a Linux setup as an afterthought but behaves like a pigeon on a chessboard rather than a package manager.
Brew is such a cute little package manager. Updating its repo every time you install something. Randomly self updating like a virus.
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#89It'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…
Good advice and beware the difference between docker export (which will fail if you lack enough storage, since it saves volumes) and docker save. Running the wrong command might knock out your only running docker server into an unrecoverable state...
Re: Show HN: Unregistry – “docker push” directly to servers without a registry
#90[deleted]