-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
"--no-hostname" option does not work as expected while building a container using podman #25002
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 13, 2025
Fixes: containers#25002 Signed-off-by: Daniel J Walsh <[email protected]>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 13, 2025
Fixes: containers#25002 Also add the ability to inspect containers for UseImageHosts and UseImageHostname. Finally fixed some bugs in handling of --no-hosts for Pods, which I descovered. Signed-off-by: Daniel J Walsh <[email protected]>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 14, 2025
Fixes: containers#25002 Also add the ability to inspect containers for UseImageHosts and UseImageHostname. Finally fixed some bugs in handling of --no-hosts for Pods, which I descovered. Signed-off-by: Daniel J Walsh <[email protected]>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 14, 2025
Fixes: containers#25002 Also add the ability to inspect containers for UseImageHosts and UseImageHostname. Finally fixed some bugs in handling of --no-hosts for Pods, which I descovered. Signed-off-by: Daniel J Walsh <[email protected]>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 14, 2025
Fixes: containers#25002 Also add the ability to inspect containers for UseImageHosts and UseImageHostname. Finally fixed some bugs in handling of --no-hosts for Pods, which I descovered. Signed-off-by: Daniel J Walsh <[email protected]>
FedeDP
pushed a commit
to FedeDP/podman
that referenced
this issue
Jan 20, 2025
Fixes: containers#25002 Also add the ability to inspect containers for UseImageHosts and UseImageHostname. Finally fixed some bugs in handling of --no-hosts for Pods, which I descovered. Signed-off-by: Daniel J Walsh <[email protected]>
@rhatdan Thanks for adding this ,tested works all good 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
If we try to build a container using podman with option
--no-hostname
as mentioned in docs https://docs.podman.io/en/latest/markdown/podman-build.1.html , it is expected that/etc/hostname
file will not be created but an empty file is created.Steps to reproduce the issue
Steps to reproduce the issue
--no-hostname
option.podman build --authfile ~/pull-secret.json --no-hostname -t "baseos" -f Containerfile
podman run -d --name baseos localhost/baseos:latest
mkdir extracted-baseos
podman export -o baseos.tar baseos
tar -xf baseos.tar -C extracted-baseos
ls extracted-baseos/etc/hostname
My container file contains image from
FROM registry.redhat.io/rhel9/rhel-bootc:latest
Describe the results you received
I can see an empty /etc/hostname file is present .
Describe the results you expected
/etc/hostname
file is not created.podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: