4 ms·
The lack of composer and Traefik support is the main reason I don't switch my personal projects to podman (work stuff is all K8s). That and neither podman nor
by rcarmo 7y ago
The lack of composer and Traefik support is the main reason I don't switch my personal projects to podman (work stuff is all K8s).
That and neither podman nor buildah being at least as easy to install on Ubuntu LTS then Docker.
Compose is just lovely for personal stuff. Swarm is also pretty decent (and easier to run for small clusters, if somewhat unstable networking-wise). Podman can't compare.
- Conan_Kudo 7y agoThere's a podman-compose project that implements the docker-compose functionality leveraging podman: https://github.com/containers/podman-compose https://github.com/containers/podman-compose
- wronglebowski 7y agoI attempted to use this for a couple very simple projects and the conversion completely fell on it's face. I tried four projects and none of them successfully converted.
- ipbabble 7y agoI'm sure that project would benefit from your feedback. What did they say? Did they understand your issues? Were they able to fix it?
- wronglebowski 7y agoHave you found kompose to be a suitable replacement for compose? I’m trying to migrate my docker projects to k8s and I’m having a hell of a time.
- steve_adams_86 7y agoI found kompose didn't give me a fluid experience with any project I tried using it with. I got endless API incompatibility issues for some reason. I'd have to dig through the docs and rewrite the files kompose generated. Even then they wouldn't always work.
- GordonS 7y agoI really feel like Docker Compose and Swarm are underrated. For running groups of related containers during development, Compose is wonderful - Compose files are simple and easy to understand even if you've never seen one before. Swarm is also good for small-scale production deployments - it's just so simple to deploy and update. "secrets" and "configs" are also really useful, but of course I see the appeal of a centralised system such as Vault for complex deployments. I've never tried to use Swarm it at scale, so don't know what kind of issues you might face that k8s would solve.
- bkircher 7y agoCan’t I just do all what docker-compose does with a Makefile and a couple of docker network create docker run and so on? With much less magic involved?
- thinkmassive 7y agoThe recommended approach for managing groups of multiple containers with podman seems to be using pods (hence the name), which can be managed by Makefiles as you describe.
- gravypod 7y agoThe benefit is standardization. If every team you join has a `docker-compose.yml` to run a local development environment you know exactly what it is, how to add things to it, etc. If every team you join has a custom solution for an extremely lightweight development environment than you need to be brought up to speed every single time. It's a similar argument to "Why do you need Makefiles when you can just write a bunch of bash files and a meta-bash file to execute each sub script based on the stat results of a list of files?"
- nickjj 7y ago> Can’t I just do all what docker-compose does with a Makefile There's a lot of value in just being able to run a set of unified Docker Compose commands and have things work the same in every case with the same YAML configuration. But technically yes you could replicate that behavior, however Docker Compose does a bunch of pretty nice things, like when you run docker-compose up it will intelligently recreate containers that changed but leave the others untouched. Then there's the whole concept of override files, etc.. It would take a fair amount of scripting to emulate all of that behavior along with getting all of the signal processing and piping multiple services to 1 terminal output acting well. Even today Docker Compose has issues with that after years of development. You should run docker-compose with --verbose one day just to see what really happens under the hood. Compose is doing a lot. For example I wrote about this a while back. It also includes an example output of running a single service app with --verbose: https://nickjanetakis.com/blog/docker-tip-60-what-really-happens-when-you-run-docker-compose-up https://nickjanetakis.com/blog/docker-tip-60-what-really-hap...
- bdcravens 7y ago> Compose is just lovely for personal stuff We use it for production, spinning up hundreds of identical setups. We just baked an AMI with a docker-compose.yml with restart: always and it is very dependable.
- weberc2 7y agoIt’s not even dependable for us on local setups; a “docker-compose up” that has to pull images will almost always throw an HTTP timeout exception from inside The Python client.
- windexh8er 7y agoAlmost guaranteed that's not a Docker compose issue.
- weberc2 7y agoHard to say. Our whole team experiences it, there are a dozen related issues in the issue tracker, and the docker-cli and Go bindings work fine while docker-compose is timing out. Based on the issues we’ve had and those files in their issue tracker, there are lots of related issues including some where the docker daemon (or perhaps the docker for mac VM) is unresponsive; we’ve definitely seen that, but as previously mentioned, we’ve also seen this issue while the daemon responds to other clients.
- ipbabble 7y agoFair points. Work is ongoing with a podman-compose. I haven't used it myself. Most of the routing work for our initial users are focused on is around Kubernetes/okd/OpenShift (and not Swarm) and so that's where those routing issues are solved. I know someone worked on a Ubuntu build but I'm not sure who is maintaining that. It would be a great place for people to contribute.