Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman-compose creating port mapping inside the container #107

Open
cbz opened this issue Feb 6, 2020 · 3 comments
Open

podman-compose creating port mapping inside the container #107

cbz opened this issue Feb 6, 2020 · 3 comments

Comments

@cbz
Copy link

cbz commented Feb 6, 2020

Hi - I'm using podman to try and start healthchecks (https://hub.docker.com/r/linuxserver/healthchecks). When started up it appears that the port mapping hasn't been created, and I can't - using netstat see any evidence of listening ports on the host, though if I do a podman ps I can see:

CONTAINER ID  IMAGE                                      COMMAND        CREATED             STATUS                 PORTS                    NAMES
c0536033cf1e  docker.io/linuxserver/healthchecks:latest                 About a minute ago  Up About a minute ago  0.0.0.0:11080->8000/tcp  hc

After doing this a number of times I then tried looking inside the container itself where I can see:

root@c0536033cf1e:/# netstat -nltp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:11080           0.0.0.0:*               LISTEN      -

From inside the container I can use wget to get at both URLs.

@barseghyanartur
Copy link
Contributor

I have a similar issue reported in podman.

I'm using Fedora 31 and it used to work well wth podman version 1.6.0, but update to 1.8.0 broke it.

@barseghyanartur
Copy link
Contributor

barseghyanartur commented Feb 12, 2020

OK, the issue solved locally, however, with tricks that were not necessary in Podman 1.6.0.

I need to forcibly stop all containers (even if podman ps does not show anything up) with podman stop --all before running podman-compose up.

Thus:

podman-compose down
podman stop --all
podman-compose up

Then it works.

@cbz
Copy link
Author

cbz commented Feb 12, 2020

As I assume it's actually an underlying podman bug I'll leave it up to you as to whether or not you want to continue to keep this open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants