Closed supermar1010 closed 4 years ago
This is related/the same issue: https://github.com/containers/podman-compose/issues/107
I'm also on fedora 31
I've also found this bug: https://github.com/containers/libpod/issues/5249
For me the port is neither opened on the host nor in the container.
Accessing the internet works from inside the container.
There were different fixes with rootlessport after 1.8.2, would it be possible to build podman from git and try with it?
Is there a container which can do the build? I'm not really keen to install all the dependencies on my server/desktop And is there a how to build file? I did not find any
Dockerfile.fedora
has the dependencies you need.
You could use it to create an image with all the build tools, and then create a container with a volume and do the go build within the container.
Same problem here with fedora 32 (podman 1.8.2). Port is not accessible on host system in rootless mode. (It works in root mode.)
@giuseppe:
I have compiled podman (libpod
) on my own on fedora 32. The issue is solved on master d6b3bc18f85236aa.
However, I'm unable to access mounted files in the container (like --mount type=bind,source=/mnt/home/aanno/scm/scm/docker-compose-files/config/solr/libs/ojdbc8-12.2.0.1.jar,destination=/opt/solr/server/lib/ext/ojdbc8-12.2.0.1.jar,ro
). Is this a known issue (e.g. still #3683 or similiar) or should I report that?
However, I'm unable to access mounted files in the container (like
--mount type=bind,source=/mnt/home/aanno/scm/scm/docker-compose-files/config/solr/libs/ojdbc8-12.2.0.1.jar,destination=/opt/solr/server/lib/ext/ojdbc8-12.2.0.1.jar,ro
). Is this a known issue (e.g. still #3683 or similiar) or should I report that?
what error are you seeing? Also, who owns that file?
I was able to fix the issue with
$ chcon -Rt svirt_sandbox_file_t /mnt/home/aanno/scm/scm/docker-compose-files/config/solr/*
like mentioned in #3683. Hence it is SELinux related. However, I think that should be at least be in the troubleshooting guide...
$ ls -Zl /mnt/home/aanno/scm/scm/docker-compose-files/config/solr
insgesamt 12
drwxrwxr-x. 3 aanno aanno unconfined_u:object_r:container_file_t:s0 19 15. Apr 17:28 collections
-rw-rw-r--. 1 aanno aanno unconfined_u:object_r:container_file_t:s0 11402 31. Mär 17:32 jetty.xml
drwxrwxr-x. 2 aanno aanno unconfined_u:object_r:container_file_t:s0 176 15. Apr 17:28 libs
I think that should be at least be in the troubleshooting guide...
would you like to open a PR to describe the issue and the solution you've found?
Well, I commented on PR #5839. If still needed afterwards, I will consider the PR.
A friendly reminder that this issue had no activity for 30 days.
@aanno Any movement on this?
I am going to close this, since it seems to be dead now. Reopen if I am mistaken.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The port is supposed to be routed to the host, but is not. See the output of
podman ps
. Port 10080(it is in a different docker-compose/pod) works but 10000 and 18081(both in the same docker-compose/pod) does not, there's no error message or similiar.Sometimes it works though, I'm not sure what triggers it that it works sometimes.
If I use a bash in the container the port 3000 is open and it returns stuff as its supposed to, so seems to be a mapping bug? In my container I'm listening on *:3000.
lsof -i -P -n | grep LISTEN
:exe 2204 jc2 9u IPv4 30349 0t0 TCP 127.0.0.1:10080 (LISTEN)
podman ps
:Steps to reproduce the issue:
Describe the results you received:
Port is not available/open
Describe the results you expected:
Port is opened and listening
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Addiotional information
I'm not sure if this is related, but when exiting the bash in the container I get this message:
I noticed something else, my system reports the ports being opened for a few seconds, then they close again.