2026-02-27 Podman 5.8

FIXME TEST DAY NAME


Date	2026-02-27 to 2026-03-06
Time	all day

Website	QA/Test Days
Matrix	#podman:fedoraproject.org^{(other clients\|?)}
Mailing list	test

Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Test Day will focus on testing podman-5.8

Fedora rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2026-708818aab1
Fedora 44:https://bodhi.fedoraproject.org/updates/FEDORA-2026-602b46427b
Fedora 43: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c623038804

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

Development - Lokesh Mandvekar (lsm5), Paul Holzinger (luap99), Mohan Boddu (mohanboddu)
Quality - Lukáš Růžička (lruzicka), Kamil Paral (kparal), Adam Williamson (adamw), Petr Sklenář (psklenar), Jaroslav Groman (jgroman)

You can chat with us on Matrix. See the infobox on top of the page to learn where to join.

Prerequisite for Test Day[edit]

A virtual machine or a bare metal machine
An installation of Fedora 44 (any Edition or Spin). Make sure to fully update your system.
- If installing a fresh system, it's recommended to use the latest nightly image (alternative download locations: local mirror, master mirror).
- Make sure you have no important data on that system. Things might go wrong -- don't do this on your production machine!
A simple way to get podman 5.8 would be sudo dnf install podman --enablerepo=updates-testing
If podman (less than 5.8) is already installed: sudo dnf update podman --enablerepo=updates-testing
Ensure running rpm -qa podman gives "podman-5.8.0-1"

How to test?[edit]

Testing Podman from a live environment is difficult and will likely wind up with the system exhausting available RAM and failing in strange ways, so we recommend you install Fedora 44 for this TestDay, or Fedora 44 container using Podman 5.8

Update your machine[edit]

Run the tests[edit]

Visit the results page.

Click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ➕ (plus) button for that test case.

Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.

Reporting bugs[edit]

Perhaps you've found an already-reported bug. Please look at:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component podman.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

exact steps you've performed (and whether you can reproduce it again)
screenshots or videos, if applicable
system journal (log), which you can retrieve by journalctl -b > journal.txt
all output in a terminal, if started from a terminal
your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Test Results[edit]

New podman 5.8 features[edit]

User	Profile	automatic db creation	parallel pulls	References
Alan Marshall	Fedora-44-20260227.n.0	warn ^[1]	pass	↑ No migration is necessary: backing database is already SQLite
alciregi	F43 x86_64 VM		pass
alciregi	Oracle Cloud Ampere A1 Instance aarch64		pass
Christopher Boni	Fedora Silverblue 43	pass
dtunma	KVM Fedora44		pass
Gary Elam	Fedora44		pass
Milan Zink	f43	pass	pass
Rob Curtis	Fedora 43 LXC		pass
Roman Gherta	F44 x86_64 MSI GF76 11SC	warn ^[1]	pass	↑ 5.7.1 was already using sqlite
smjagtap	KVM Fedora44		pass ^[1]	↑ worked as expected
Yosuke Matsumura	Kinoite Nightly 44-20260301		pass

Basic Test[edit]

User	Profile	image pull	container	list container	remove container	inspect container	save container	References
Alan Marshall	Fedora-44-20260227.n.0	pass	pass	pass	pass	pass	pass
alciregi	F43 x86_64 VM	pass	pass	pass	pass	pass	pass
alciregi	Oracle Cloud Ampere A1 Instance aarch64	pass	pass	pass	pass
dtunma	KVM Fedora44	pass	pass	pass	pass	pass	pass ^[1]	↑ save w/ podman 5.7.1 and load w/ podman 5.8.0
Gary Elam	Fedora44	pass ^[1]	pass	pass ^[2]	pass	pass	pass ^[3]	↑ Longtime Linux hobbyist now retired learning a lot. Thanks for the opportunity! ↑ podman ps showed column headers and nothing else, expected. podman ps -a shows exited container. Took a minute to realize I needed to remove '--rm' from the run command for podman ps -a to function properly. Not sure if this is expected or not. ↑ All elements worked except I only have podman 5.8 running. Was able to save as .tar and view with podman images
George Orobet	f44	pass	pass	pass	pass	pass	pass
Milan Zink	f43	pass	pass	pass	pass	pass	pass
Paolo Junior Angeloni	Fedora-44-20260226.n.0	pass ^[1]	pass ^[2]	pass	pass ^[3]	pass	pass ^[4]	↑ successfully pulled fedora image from registry.fedoraproject.org/fedora and quay.io/fedora/fedora ↑ also ran in detached mode and attached to running container ↑ batch deletion (--all) works ↑ saved existing image, removed all existing containers and images. loaded saved .tar file successfully
Roman Gherta	F44 x86_64 MSI GF76 11SC	pass	pass	pass	pass	pass	pass
smjagtap	KVM Fedora44	pass ^[1]	pass ^[2]	pass ^[3]	pass ^[4]	pass ^[5]	warn ^[6]	↑ Able to pull latest Fedora release 43 ↑ new container starts without error, providing access to a bash shell. and got removed due to --rm post exit ↑ Got expected result ↑ Got expected result ↑ Got expected result ↑ Not clear why we need to test with Podman 5.2 as testing is for podman 5.8
Yosuke Matsumura	Kinoite Nightly 44-20260301	pass	pass	pass	pass	pass

Advanced[edit]

User	Profile	zstd	composefs	system shutdown	virtiofs
Alan Marshall	Fedora-44-20260227.n.0		pass	pass	pass
dtunma	KVM Fedora44		pass	pass	pass
Paolo Junior Angeloni	Fedora-44-20260226.n.0			pass	pass
Roman Gherta	F44 x86_64 MSI GF76 11SC	pass	pass	pass	pass

[1] No migration is necessary: backing database is already SQLite

[2] 5.7.1 was already using sqlite

[3] worked as expected

[4] save w/ podman 5.7.1 and load w/ podman 5.8.0

[5] Longtime Linux hobbyist now retired learning a lot. Thanks for the opportunity!

[6] s showed column headers and nothing else, expected. podman ps -a shows exited container. Took a minute to realize I needed to remove '--rm' from the run command for podman ps -a to function properly. Not sure if this is expected or not.

[7] All elements worked except I only have podman 5.8 running. Was able to save as .tar and view with podman images

[8] successfully pulled fedora image from registry.fedoraproject.org/fedora and quay.io/fedora/fedora

[9] so ran in detached mode and attached to running container

[10] tch deletion (--all) works

[11] saved existing image, removed all existing containers and images. loaded saved .tar file successfully

[12] Able to pull latest Fedora release 43

[13] w container starts without error, providing access to a bash shell. and got removed due to --rm post exit

[14] Got expected result

[15] Got expected result

[16] Got expected result

[17] Not clear why we need to test with Podman 5.2 as testing is for podman 5.8

[1]

[1]

[1]

[1]

[1]

[2]

[3]

[1]

[2]

[3]

[4]

[1]

[2]

[3]

[4]

[5]

[6]

Search

Test Day:2026-02-27 Podman 5.8

Contents