You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker (checked in old Debian 10) allows one to start image without /etc/hosts file without errors (i.e. when image contains only static binary).
Podman (checked 4.3.1+ds1-8+deb12u1 in Debian 12) with base_hosts_file = "image" throws error
Error: creating hosts file for container [...]: failed to create new hosts file: open /var/lib/containers/[...]/merged/etc/hosts: no such file or directory
with same image.
Steps to reproduce the issue
Steps to reproduce the issue
Set base_hosts_file = "image" in containers.conf.
Start container from image that does not contain /etc/hosts file.
Describe the results you received
Error is thrown and container is not started.
Describe the results you expected
Podman with base_hosts_file = "image" allows to run images with no /etc/hosts file with empty base /etc/hosts content. No error is thrown (similar to docker).
Can you test with the latest podman version, 4.3 is quite old now. Or can you provide a basic image where this is the case.
I have tried to reproduce this with podman run --hosts-file image ... with a locally image that does not have the hosts file in it and it still worked fine.
Issue Description
Docker (checked in old Debian 10) allows one to start image without
/etc/hosts
file without errors (i.e. when image contains only static binary).Podman (checked 4.3.1+ds1-8+deb12u1 in Debian 12) with
base_hosts_file = "image"
throws errorwith same image.
Steps to reproduce the issue
Steps to reproduce the issue
base_hosts_file = "image"
incontainers.conf
./etc/hosts
file.Describe the results you received
Error is thrown and container is not started.
Describe the results you expected
Podman with
base_hosts_file = "image"
allows to run images with no/etc/hosts
file with empty base /etc/hosts content. No error is thrown (similar to docker).podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
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: