3 ms·
> In fact, a global system daemon should not be needed. Either users should be able to run their own daemons or container management should avoid having a daemo
by aloknnikhil 7y ago
> In fact, a global system daemon should not be needed. Either users should be able to run their own daemons or container management should avoid having a daemon at all, by storing container state in a shared database.
Absolutely love Podman. You can even define registries to work with docker hub, easily.
https://podman.io https://podman.io
- nikisweeting 7y agoYeah but no docker-compose support :/ dealbreaker for us. Theres an alpha podman-compose project but we couldn't get it running.
- likeclockwork 7y agoYou really don't need it since podman has pods of containers that communicate with each other. You can export and playback the pods as kubernetes yaml.. but I just use a bash script + an environment file to configure, create and launch pods. What else is docker-compose really doing for you?
- nikisweeting 7y agoOur entire company runs on like ~20 docker-compose files. It's a super elegant way to describe collections of containers without the management overhead of Kubernetes. We've had nothing but good experiences with compose, and lots of headaches with Docker swarm and K8s.
- dharmab 7y agoBoth Podman and CRI-O support Pods, which can fill the same use case as docker-compose
- nikisweeting 7y agoWhich require kubernetes, which requires a full-time team member just to manage. Docker-compose has been a lifesaver for low-complexity declarative service management on our self-hosted systems.
- jsilence 7y agoInteresting! Are there management tools like Portainer available? Or would, even better, Portainer work with Podman?
- nullify88 7y agoRegarding portainer working with podman, not yet it seems. Here's a gh case for it https://github.com/portainer/portainer/issues/2991 https://github.com/portainer/portainer/issues/2991