[608882827] Upstream Reporter: Mildred Ki'Lya
Upstream issue status: Closed
Upstream description:

I'm trying to use podman-compose to develop a compose file for an application, and I'm having issues when I try to start single containers after podman-compose up failed. I'm having an issue like that:

$ sudo podman-compose start web
using podman version: podman version 1.8.2
podman start myapp_web_1
Error: unable to start container "myapp_web_1": cannot listen on the TCP port: listen tcp4 :3000: bind: address already in use
125

And when I look, port 3000 is held by conmon that keeps running for the previous version of the same container that exited long ago.

I believe conmon should not keep opened ports for stopped containers.

Version information (all running on Fedora 32 silverblue):

• podman-compose-0.1.7.dev0
• podman-1.8.2-2.fc32.x86_64
• conmon-2.0.14-1.fc32.x86_64