psviderski

7 ms·

31.
by psviderski 10mo ago
That’s awesome if k3s works for you, nothing wrong with this. You’re simply not the target user then.
32.
by psviderski 10mo ago
There is an open issue that confirms enabling ipv6 for containers works: https://github.com/psviderski/uncloud/issues/126 But this hasn’t been enabled by default. What specifically do you mean by ipv6 support
33.
by psviderski 10mo ago
I took some inspiration from Kamal, e.g. the imperative model but kamal is more a deployment tool. In addition to deployments, uncloud handles clustering - connects machines and containers together. Service containers can discover other ser
34.
by psviderski 10mo ago
Hey, creator here. Thanks for sharing this! Uncloud[0] is a container orchestrator without a control plane. Think multi-machine Docker Compose with automatic WireGuard mesh, service discovery, and HTTPS via Caddy. Each machine just keeps a
35.
by psviderski 1y ago
Check out https://github.com/psviderski/uncloud I'm building. Multi-machine deployments and a private WireGuard network spanning locations (even behind a NAT) are its core capabilities.
36.
by psviderski 1y ago
Exactly, although my main motivation was to reduce the distinction between docker engine and docker registry. To make it possible for a user to push/pull to the docker daemon as if it was a registry, hence a registry wrapper. This is a
37.
by psviderski 1y ago
They're unbundled already. You can run unregistry as a standalone service and use your own way to push/pull from it: https://github.com/psviderski/unregistry?tab=readme-ov-file#...
38.
by psviderski 1y ago
The problem with running a registry locally is that Docker doesn't provide an API to get individual image layers to be able to build a registry API on top. You have to hook into the containerd Docker uses under the hood. You can't
39.
by psviderski 1y ago
You're the OG! Hats off, mate. It's a bummer docker still doesn't have an API to explore image layers. I guess their plans to eventually transition to containerd image store as the default. Once we have containerd image store
40.
by psviderski 1y ago
Hey Solomon, thank you for sharing your thoughts, love your work! 1. Yeah agreed, it's a bit of a mess that we have at least three different file system layouts for images and two image stores in the engine. I believe it's still n
41.
by psviderski 1y ago
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?
42.
by psviderski 1y ago
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 d
43.
by psviderski 1y ago
Wow ttl.sh is a really neat idea, thank you for sharing!
44.
by psviderski 1y ago
I guess you're asking about the registry part (not 'pussh' command). It exposes the containerd image store as standard registry API so you can use any tools that work with regular registry to pull/push images to it. You
45.
by psviderski 1y ago
Ah neat I didn't know that podman has 'image scp'. Thank you for sharing. Do you think it was more straightforward to implement this in podman because you can easily access its images and metadata as files on the file system
46.
by psviderski 1y ago
I don't see a reason to not adopt this in Kamal. I'm also building Uncloud that took a lot of inspiration from Kamal, please check it out. I will integrate unregistry into uncloud soon to make the build/deploy process a breez
47.
by psviderski 1y ago
Yep, I'm familiar with Kamal and it actually inspired me to build Uncloud using similar principles but with more cluster-like capabilities. I built Unregistry for Uncloud but I belive Kamal could also benefit from using it.
48.
by psviderski 1y ago
That's an interesting idea. I don't think you can create a subcommand/plugin for compose but creating a 'docker composepussh' command that parses the compose file and runs 'docker pussh' should be possible
49.
by psviderski 1y ago
Met too, you're welcome! Please create an issue on github if you find any bugs
50.
by psviderski 1y ago
I'm glad the idea of uncloud resonated with you. Feel free to join our Discord if you have questions or need help
51.
by psviderski 1y ago
For sure, it's always a tradeoff and it's great to have options so you can choose the best tool for every job.
52.
by psviderski 1y ago
That's a valid concern. You can very easily give it whatever name you like. Docker looks for `docker-COMAND` executables in ~/.docker/cli-plugins directory making COMMAND a `docker` subcommand. Rename the file to whatever you
53.
by psviderski 1y ago
You need a containerd on the remote end (Docker and Kubernetes use containerd) and anything that speaks registry API (OCI Distribution spec: https://github.com/opencontainers/distribution-spec ) on the client. Unregistr
54.
by psviderski 1y ago
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
55.
by psviderski 1y ago
Thank you! Can you please clarify what kind of support you mean for docker compose?
56.
Show HN: Unregistry – “docker push” directly to servers without a registry(github.com)
726 points by psviderski 1y ago|164 comments
57.
by psviderski 1y ago
Thanks! For zero-downtime deploys, it does simple rolling updates one container at a time in a similar way k8s or swarm does it. It starts the new container alongside the old one, waits for it to become healthy, Caddy picks it up and update
58.
by psviderski 1y ago
I'm actually building something in between Docker and Kubernetes: https://github.com/psviderski/uncloud . Like you I wanted that middle ground without the operational overhead. It's basically Docker-like CLI a
59.
by psviderski 1y ago
Can you still justify K8s even if you need to jump from one cloud/dedicated instance to say 2-3 for reliability?
60.
by psviderski 1y ago
After a decade of professionally working with container orchestrators like Kubernetes and ECS I quit my job to build Uncloud — an open source lightweight version of those [1]. I want the tool to bring me joy when I use it, in a similar way

More ›