3 ms·
I feel like podman is proving that you don't really need the api daemon and a porcelain over runc with a one-off process supervisor is sufficient for a good num
by Spivak 7y ago
I feel like podman is proving that you don't really need the api daemon and a porcelain over runc with a one-off process supervisor is sufficient for a good number of workloads.
Being able to run containers like any other process and leave the lifecycle management to systemd is actually really nice.
- freedomben 7y agoCould not agree more. As a Fedora user I was mildly intrigued when Podman showed up, I played with it briefly but stopped because most of my projects used docker-compose, which doesn't work with Podman. When I went to work at Red Hat I decided to really try Podman, and I love it now. Once I discovered that Podman supports Kubernetes Pods (same YAML and all) I realized how clunky docker-compose actually is. Since most of my projects now run in K8s anyway, it's awesome to have the app run as a Pod locally so it can easily be tested with any sidecars in the same configuration. There are still uses for docker-compose, and I don't expect it to disappear from my life completely any time soon, but Podman does have a great place in my toolkit.
- throwaway8941 7y agopodman-compose works fine for me, despite being advertised as "still under development". https://github.com/containers/podman-compose https://github.com/containers/podman-compose
- freedomben 7y agoThanks, it might be time for me to give it another try.
- terrywang 7y agopodman-compose works better than expected, however, it is NoT a "drop-in" replacement for docker-compose, at least now.
- jacobr1 7y agoYep. Because the use case that seems to be most common is not running untrusted containers, but rather something more like static compilation, but with ruby or javascript code. So on a single machine just considering it another process, but with better isolation of dependencies is (including encapsulation of distinct processes and in-container network activity) is actually the use case. And once we scale up to multiple machines for resource needs, something like k8s starts to make sense, because it just moves the abstraction to the cluster level rather than the machine. The more you get k8s to be a "cluster systems" the saner the management.
- SahAssar 7y agoSystemd has some pretty nice sandboxing settings built in if you (like me) prefer to not use docker-like containers. With stuff like RootImage and the various isolation settings you can have a configurably sandboxed container right in systemd. Or just use systemd-nspawn if you want it more preconfigured.
- dnautics 7y agodo you know if any of these non-daemon containers give you network isolation, and if so, how they do it? Not that most workloads need it.
- koffiezet 7y agoThere are imho 3 key features what made Docker great: * the combination of all technologies touched here in the example, but it's missing a very important-one: the layered filesystem * A defined packaging format and way of distributing images * Having an API to talk to these things easily. That is what kickstarted and revolutionised the container space, but there were still many technology gaps and questions. They tried to put everything in one single tool, which was a double-edged sword I think: it made usage easy which accelerated adoption, but also caused it being a big 'monolith' project, which is a bit ironic given that it ended up being extremely suitable for micro-service architectures. For me as an early adopter, it was very clear from the start that the main problem was how do you actually deploy this in production. Docker saw a very large part of the conceptual bigger picture, but they had any clue how to address this, but to be fair, very few did. Right now, a lot of lessons have been learned, and standards have been created in the container space. Nowadays, for production loads, k8s has become the de-facto standard container api, and Docker itself doesn't really carry that much weight anymore, the runtime itself isn't important anymore. It being podman, runc, or still a full-blown docker? I couldn't really care less. Docker's stronghold will remain the development environment for a while though, just due to the massive amount of resources and easy to use solutions out-there...