31–40 of 88 posts
This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.
Docker?
Earlier quoted context omitted.
> In fact, I'd prefer if the tools you mentioned used something else besides yaml. To be fair, most of the popular DevOps tools can work with JSON instead of YAML just fine. And JSON can be easily generated from almost anywhere. I don't think you can work with systemd syntax as easily.
Out of curiosity, do you know any tools that can't use JSON but can use YAML? JSON is supposed to be valid YAML.
This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.
> Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack. Docker?
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
This is actually a pretty natural fit, imo. Docker containers are basically processes with fat runtimes, and container orchestration layers are essentially glorified process supervisors. At the same time, most Linux systems already come with a pretty fancy process supervisor. Personally, I think writing systemd units from scratch is already pretty easy. But it makes sense that Linux software which often integrates wi…
There is a little more to container orchestration runtimes. Would say at this time they are akin to a badly designed, distributed linker (I'm saying this as someone who did not fully buy into this stuff, but I see that it solves some problems)
[1]: https://github.com/containers/ansible-podman-collections
I was just cursing a lot setting up a single node with my default stack. I’m going to try this tomorrow, because containers are so useful, but I just don’t want to deal with K8s on anything that I run myself.
not even k3s?
This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.
> Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack. Docker?
Earlier quoted context omitted.
not even k3s?
Does Kubernetes support swap files yet? Last time I checked it was still a beta flag :(
I work with data science tools that require 16G of RAM eac for hundreds of users, and Kubernetes was an appalling choice of platform for it. It has cost the org millions a year more than it needed to, given the actual usage profiles involved. Unsurprising that big contributors to k8s have been.. companies selling compute.