3 ms·
I've started using podman for my personal projects where I want to deploy just a single service in perhaps a couple of containers on a VM. I rebooted a box one
by alias_neo 7y ago
I've started using podman for my personal projects where I want to deploy just a single service in perhaps a couple of containers on a VM.
I rebooted a box one time, and some sort of tracking for the podman networking decided that my listening port was still in use even though no container was running. The only way I fixed it was to uninstall the networking tool podman uses (I forget it's name; slirp4ns or something) and podman itself then reinstall and start again.
I use docker daily, professionally, it has it's issues, but a lack of docker-compose like files and anecdotal reliability issues I've seen, I can't see it taking over from, or even competing with Docker for some time yet.
- ipbabble 7y agoI'm sure that project would benefit from your feedback and information on what looks like a bug. What did upstream Podman community say? Did they understand your issues? Were they able to reproduce the error? Were they able to fix it?
- alias_neo 7y agoHonestly, I haven't been in touch with the community yet. I needed it working quickly so I solved my issue and I moved on. If it happens again, I'll be expecting it and I'll collect data to report it.