3 ms·
I wonder if users of non-RPM distros would be eager use these tools. Even if these tools are a little better (maybe they are), my guess would be only medium siz
by Proven 7y ago
I wonder if users of non-RPM distros would be eager use these tools. Even if these tools are a little better (maybe they are), my guess would be only medium sized K8s users may find it worthwhile to switch.
Large users usually build their own, and small users are lazy to chase incremental improvements (if they do change they'll move to public build services).
- pabs3 7y agoIt looks like at least two people want buildah/podman on non-RPM distros. buildah recently entered Debian unstable and podman is in the process of being packaged: https://metadata.ftp-master.debian.org/changelogs//main/g/golang-github-containers-buildah/unstable_changelog https://metadata.ftp-master.debian.org/changelogs//main/g/go... https://bugs.debian.org/930440 https://bugs.debian.org/930440
- detaro 7y ago(without first-hand experience with it) I could see it being popular with people not going all-in with containers. We have a few machines with services that are conventionally managed and a few services being stuffed into docker containers, and it feels slightly odd that some services are managed through systemd and some through docker commands.
- viraptor 7y agoWhy not provide systemd service files for your docker services as well?
- detaro 7y agoguess one could use --interactive calls to docker to keep the process attached maybe? Haven't thought of that before.
- mclehman 7y agoI ended up writing a mostly-declarative tool for managing my mix of docker-composed and init-system-ed services at home when that got too unmanageable.