-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
REST APIv2 - rootless - hostname not added to /etc/hosts #7934
Comments
related to testcontainers/testcontainers-java#2088 and #7235 |
@psakar could you confirm if you are running the service as rootfull or rootless? |
@psakar im asking because i just ran your reproducer with upstream main branch and it ran correctly as rootful. |
@baude rootless (as noted in title) |
@psakar ty! i cannot believe i missed that. The # instead of $ was probably confusing me. I'll take another peek. |
Ok, I can reproduce this. |
when using the compatibility mode as rootless, containers that were created were not setting their host names correctly due to the netmode not being set. Fixes: containers#7934 Signed-off-by: baude <[email protected]>
when using the compatibility mode as rootless, containers that were created were not setting their host names correctly due to the netmode not being set. Fixes: containers#7934 Signed-off-by: baude <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Container created via REST APIv2 is unable to resolve its hostname because the assigned hostname is missing in container /etc/hosts
Steps to reproduce the issue:
Describe the results you received:
Last two lines from file /etc/hosts from my laptop
Describe the results you expected:
(Value 3ff0b3519d00 would be different ...)
Additional information you deem important (e.g. issue happens only occasionally):
May be because netmode is not set ? Applying following patch fixes the issue (most probably wrong, just to test)
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes (not tested with master)
Additional environment details (AWS, VirtualBox, physical, etc.):
laptop
The text was updated successfully, but these errors were encountered: