-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.
Description
Failing in ubuntu 2204, remote, with cgroupsv1 and runc:
podman checkpoint and restore container out of and into pod (ipc,net,uts,pid)
...
# podman-remote [options] container restore --pod NEW-POD-ID -i /tmp/checkpoint-CONTAINER-ID.tar.gz
Error: cannot restore pod container without --pod
(The discerning reader will note that --pod is specified in the command line). That error seems to come from
podman/pkg/checkpoint/checkpoint_restore.go
Lines 59 to 61 in 039deec
| if ctrConfig.Pod != "" && restoreOptions.Pod == "" { | |
| return nil, errors.New("cannot restore pod container without --pod") | |
| } |
Earlier in that test, I see this warning:
# podman-remote [options] container checkpoint -e /tmp/checkpoint-CONTAINER-ID.tar.gz CONTAINER-ID
time="2022-07-20T21:07:00Z" level=warning msg="lstat /sys/fs/cgroup/devices/machine.slice/machine-libpod_pod_OLD-POD-ID.slice/libpod-CONTAINER-ID.scope: no such file or directory"
So, yeah, seems to be cgroups-related. Something we just never tested because we haven't been testing runc.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.