Skip to content

Podman 5.5.1-1 segfaults when dealing with lockfiles #26469

Open
@jdoss

Description

@jdoss

Issue Description

I rebooted my workstation to reboot into a new kernel and now none of my rootless podman containers will start. I can't even run podman ps -a. Linger is enabled. I am using the BTRFS storage driver.

Downgrading to 5.4.1 deals with the lock files no problem and fixed the issue. I was able to upgrade back to 5.5.1 and run my containers again.

Steps to reproduce the issue

Steps to reproduce the issue

  1. Not sure
  2. Reboot
  3. Log into GNOME
  4. None of my containers start
  5. podman ps -a segfaults
  6. Wife yells at me because she can't watch her stories on Jellyfin :(
  7. Downgrade to 5.4.1
  8. Run podman version to fix the lock files
  9. Upgrade back to 5.5.1

Describe the results you received

See segfault below.

Describe the results you expected

Many containers running.

podman info output

$ rpm -q podman
podman-5.5.1-1.fc42.x86_64

Podman info and version also segfault

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

No response

Metadata

Metadata

Assignees

Labels

5.5kind/bugCategorizes issue or PR as related to a bug.regressiontriagedIssue has been triaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions