Bug 2173082 - Podman containers do not start after upgrade to v4.4.1
Summary: Podman containers do not start after upgrade to v4.4.1
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.9
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks: 2173089 2176833
TreeView+ depends on / blocked
 
Reported: 2023-02-23 21:53 UTC by Tom Sweeney
Modified: 2023-08-18 09:17 UTC (History)
12 users (show)

Fixed In Version: podman-4.6.1-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2173089 2176833 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 17839 0 None closed [v4.4.1-rhel] Vendor c/storage v1.45.4 2023-08-18 09:10:49 UTC
Red Hat Issue Tracker RHELPLAN-149856 0 None None None 2023-02-23 21:56:35 UTC
Red Hat Issue Tracker RHELPLAN-149857 0 None None None 2023-02-23 21:56:37 UTC

Description Tom Sweeney 2023-02-23 21:53:36 UTC 
Description of problem:
After upgrading from Podman v4.2.1 to 4.4.1, no Podman containers will start.

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


How reproducible:

Upgrade Podman v4.2.1 to v4.4.1 with existing containers and try to run them afterward.

Steps to Reproduce:
1.
2.
3.

Actual results:  
Error: filesystem type 0x13372fc1 reported for /var/lib/containers/storage is not supported with 'overlay': backing file system is unsupported for this graph driver

Expected results:

Successful completion of the podman run command.

Additional info:  Reported on GitHub: https://github.com/containers/storage/issues/1511
Comment 3 Tom Sweeney 2023-03-17 15:37:30 UTC 
Setting to Post and assigning to @jnovy for any further BZ and triaging needs.  Fixed upstream with https://github.com/containers/podman/commit/9d93486d21890dd844fef158d0860ace1357f5ae
Comment 4 Jindrich Novy 2023-03-17 17:47:43 UTC 
Tom, this needs to be merged to v4.4.1-rhel upstream branch too in order to consider this to 9.2.0 0day.
Note You need to log in before you can comment on or make changes to this bug.