Live data from Hacker News

Uncloud - Tool for deploying containerised apps across servers without k8s

uncloud.run

141–150 of 189 posts

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#141
post #100
post #18

Earlier quoted context omitted.

I can only speak for myself, but I considered a few options, including "simple k8s" like [Skate]( https://skateco.github.io/ ), and ultimately decided to build on uncloud. It was as much personal "taste" than anything, and I would describe the choice as similar to preferring JSON over XML. For whatever reason, kubernetes just irritates me. I find it unpleasant to use. And I don't think I'm unique in that regard.

> For whatever reason, kubernetes just irritates me. I find it unpleasant to use. And I don't think I'm unique in that regard. I feel the same. I feel like it's a me problem. I was able to build and run massive systems at scale and never used kubernetes. Then, all of a sudden, around 2020, any time I wanted to build or run or do anything at scale, everywhere said I should just use kubernetes. And then when I wanted t…

It’s a nice portable target, with very well defined interfaces. It’s easy to start with and pretty easy to manage if you don’t try to abuse it.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#142
post #4

Earlier quoted context omitted.

"I keep seeing teams reach for K8s when they really just need to run a bunch of containers across a few machines" Since k8s is very effective at running a bunch of containers across a few machines, it would appear to be exactly the correct thing to reach for. At this point, running a small k8s operation, with k3s or similar, has become so easy that I can't find a rational reason to look elsewhere for container "orche…

k3s makes it easy to deploy, not to debug any problems with it. It's still essentially adding few hundred thousand lines of code into your infrastructure, and if it is a small app you need to deploy, also wasting a bit of ram

"not to debug any problems with it"

K3s is just a repackaged, simplified k8s distro. You get the same behavior and the same tools as you have any time you operate an on-premises k8s cluster, and these, in my experience, are somewhere between good and excellent. So I can't imagine what you have in mind here.

"It's still essentially adding few hundred thousand lines of code into your infrastructure"

Sure. And they're all there for a reason: it's what one needs to orchestrate containers via an API, as revealed by a vast horde of users and years of refinement.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#143
post #123

This look really neat and great! Amazing job! BTW just looking at other variations on the theme: - https://dokploy.com/ - https://coolify.io/ - https://demo.kubero.dev/ Feel free to add more.

There's a good list here: https://dbohdan.com/self-hosted-paas

I'm always looking for new alternatives there, I've recently tried Coolify but it didn't feel very polished and mostly clunky. I'm still happy with Dokku at this point but would love to have a better UI for managing databases etc.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#144

I'm a docker swarm user, and this is the first alternative that looks interesting to me! Some questions I have based on my swarm usage: - do you plan to support secrets? - with swarm and traefik, I can define url rewrite rules as container labels. Is something equivalent available? - if I deploy 2 compose 'stacks', do all containers have access to all other containers, even in the other stack?

Secrets -- yes, it's being tracked here: https://github.com/psviderski/uncloud/issues/75 Compose configs are already supported and can be used to inject secrets as well, but there'll be no encryption at rest there in that case, so might not be ideal for everyone.

Regarding questions 2 and 3, the short answers are "not at the moment" and "yes, for now", here's a relevant discussion that touches on both points: https://github.com/psviderski/uncloud/discussions/94

Speaking of Swarm and your experience with it: in your opinion, is there anything that Swarm lacks or makes difficult, that tools like Uncloud could conceptually "fix"?

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#145

This is extremely interesting to me. I've been using docker swarm, but there is this growing feeling of staleness. Dokku feels a bit too light, K8 absolutely too heavy. This proposition strikes my sweet spot - especially the part where I keep my existing docker compose declarations

Dokku Maintainer here.

Would love to hear about what you think is "light" about Dokku if you have some time for feedback.

Regardless, hope you find a tool you're happy with :)

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#146
post #143
post #123

This look really neat and great! Amazing job! BTW just looking at other variations on the theme: - https://dokploy.com/ - https://coolify.io/ - https://demo.kubero.dev/ Feel free to add more.

There's a good list here: https://dbohdan.com/self-hosted-paas I'm always looking for new alternatives there, I've recently tried Coolify but it didn't feel very polished and mostly clunky. I'm still happy with Dokku at this point but would love to have a better UI for managing databases etc.

Okay could you please share your thoughts as a user:

- What databases you want to work with?

- What functionality you want from such a UI?

- What database size we are talking here?

Asking because I am tinkering with a similar idea.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#147

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 p2p-synced copy of cluster state (using Fly.io's Corrosion), so there's no quorum to maintain. I’m building Uncloud after years of managing Kubernetes in small envs and at a unicor…

We have similar backgrounds, and I totally agree with your k8s sentiment. But I wonder what this solves? Because I stopped abusing k8s and started using more container hosts with quadlets instead, using Ansible or Terraform depending on what the situation calls for. It works just fine imho. The CI/CD pipeline triggers a podman auto-update command, and just like that all containers are running the latest version. So w…

Uncloud seems much easier to manage than writing your own ansible or terraform.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#148
post #100
post #18

Earlier quoted context omitted.

I can only speak for myself, but I considered a few options, including "simple k8s" like [Skate]( https://skateco.github.io/ ), and ultimately decided to build on uncloud. It was as much personal "taste" than anything, and I would describe the choice as similar to preferring JSON over XML. For whatever reason, kubernetes just irritates me. I find it unpleasant to use. And I don't think I'm unique in that regard.

> For whatever reason, kubernetes just irritates me. I find it unpleasant to use. And I don't think I'm unique in that regard. I feel the same. I feel like it's a me problem. I was able to build and run massive systems at scale and never used kubernetes. Then, all of a sudden, around 2020, any time I wanted to build or run or do anything at scale, everywhere said I should just use kubernetes. And then when I wanted t…

I mean the real answer it is got easily to deploy k8s so the justification for not using it kinda vanished.

Re: Uncloud - Tool for deploying containerised apps across servers without k8s

#150
post #4

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 p2p-synced copy of cluster state (using Fly.io's Corrosion), so there's no quorum to maintain. I’m building Uncloud after years of managing Kubernetes in small envs and at a unicor…

"I keep seeing teams reach for K8s when they really just need to run a bunch of containers across a few machines" Since k8s is very effective at running a bunch of containers across a few machines, it would appear to be exactly the correct thing to reach for. At this point, running a small k8s operation, with k3s or similar, has become so easy that I can't find a rational reason to look elsewhere for container "orche…

Except it isn't just "a way to run a bunch of containers across a few machines".

It seems that way but in reality "resource" is a generic concept in k8s. K8s is a management/collaboration platform for "resources" and everything is a resource. You can define your own resource types too. And who knows, maybe in the future these won't be containers or even linux processes? Well it would still work given this model.

But now, what if you really just want to run a bunch of containers across a few machines?

My point is, it's overcomplicated and abstracts too heavily. Too smart even... I don't want my co workers to define our own resource types, we're not at a google scale company.

Post reply on HN