Bug 1763868 - Existing Containers Unusable after Fedora 30 -> 31 Upgrade
Summary: Existing Containers Unusable after Fedora 30 -> 31 Upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: podman
Version: 31
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Heon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F31FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2019-10-21 19:15 UTC by Matthew Heon
Modified: 2019-10-31 13:21 UTC (History)
14 users (show)

Fixed In Version: podman-1.6.2 podman-1.6.2-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-23 18:38:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthew Heon 2019-10-21 19:15:59 UTC
Description of problem:

After an upgrade from Fedora 30, existing containers are unusable, returning errors about 

Version-Release number of selected component (if applicable):

podman-1.6.1-2.fc31.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Start with a fresh F30 install
2. Create several containers with `podman create` - e.g. `podman create -t -i --name testctr alpine sh`
3. dnf system-upgrade to F31
4. Run `podman start` on a container

Actual results:

```
ERRO[0000] oci runtime "runc" does not support CGroups V2: use system migrate to mitigate                                                                     │·······························
Error: unable to start container "e79b7fbb53a7": this version of runc doesn't work on cgroups v2: OCI runtime error     
```

Expected results:

A shell installed in the container

Additional info:

The `system migrate` command recommended by the error message does not fix the issue. The actual fix was introduced in `podman-2:1.6.2-2.fc31.x86_64`.

Comment 1 Daniel Walsh 2019-10-21 19:18:21 UTC
Fixed in podman 1.6.2

Comment 2 Fedora Blocker Bugs Application 2019-10-21 19:25:22 UTC
Proposed as a Freeze Exception for 31-final by Fedora user baude using the blocker tracking app because:

 This impacts all silverblue upgrades from 30-31.  Any containers created on 30 will not run on 31 immediately following the upgrade. This includes rootfull and rootless containers.  Any systemd controlled containers that start on boot will fail unless they are recreated by the unit files on the fly as well.  Error messages for the failures are not handled well in the current version of podman.  podman-2:1.6.2-2 has excellent error messages and handles the migration of containers.

Comment 3 Matthew Heon 2019-10-21 19:25:58 UTC
The proper fix here is to run `podman system migrate --runtime crun` - but this flag to `podman system migrate` is only available from 1.6.2 on.

Comment 4 Adam Williamson 2019-10-21 19:30:29 UTC
+1 FE to have upgrades working smoothly ASAP.

Comment 5 Dusty Mabe 2019-10-21 19:30:57 UTC
+1 FE

Comment 6 Geoffrey Marr 2019-10-21 19:31:31 UTC
Seems FE-worthy, especially since there is already a fix. +1FE from me.

Comment 7 Geoffrey Marr 2019-10-21 19:37:45 UTC
From sgallagh, per conversation on #fedora-qa:

+1 FE

Comment 8 Mohan Boddu 2019-10-21 19:40:01 UTC
+1 FE

Comment 9 Zbigniew Jędrzejewski-Szmek 2019-10-21 20:02:55 UTC
+1 FE

Comment 10 Adam Williamson 2019-10-21 21:53:02 UTC
That's +6, setting accepted.

Comment 11 Dusty Mabe 2019-10-22 02:08:06 UTC
We need someone to attach this bug (accepted FE) to this bodhi update [1] so the update can be promoted into a RC build.

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2019-48a3b3e29a

Comment 12 Fedora Update System 2019-10-22 02:13:05 UTC
FEDORA-2019-48a3b3e29a has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-48a3b3e29a

Comment 13 Fedora Update System 2019-10-23 18:38:40 UTC
podman-1.6.2-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 14 cedric 2019-10-31 13:21:14 UTC
cgroup v2 change

a temporary solution

options to add to the kernel
sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"
shutdown -r now

the container will start after


to remove the option
sudo grubby --update-kernel=ALL --remove-args="systemd.unified_cgroup_hierarchy=0"
shutdown -r now


Note You need to log in before you can comment on or make changes to this bug.