/etc/hosts becomes empty after checkpoint and restore #22901
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
Checkpoint then restore a container causes the
/etc/hosts
file become empty, which causes problem to localhost network. This issue seems to only happen in podman v5. I never hit such issue with v4 before.The
/etc/hosts
before checkpoint:After restore:
I have tried both
netavark
andcni
backend, and both have this issue. This issue can be easily reproduce use a simple python program(see below)Host OS:
CentOS Stream 9
, Rocky Linux 9 (tried on both, and both have this issue)Kernel:
5.14.0-391.el9.x86_64
EC2 instance: t2.2xlarge
conmon
version: 2.1.0, commit: 8ef5de138efb6f0aad657082cdea22cf037792cbcrun
version: 1.15 (also triedrunc v1.1.12
)netavark
version: 1.10.3Steps to reproduce the issue
Steps to reproduce the issue
test.py
:/etc/hosts
:/etc/hosts
, now its empty:Describe the results you received
/etc/hosts
file becomes empty after restore.Describe the results you expected
/etc/hosts
should remain the same as before the checkpoint.podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
I'm using AWS EC2 instance(
t2.2xlarge
, andg4dn.4xlarge
).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: