2024-11-01 Podman 5.3

Podman 5.3


Date	2024-11-01 to 2024-11-08
Time	all day

Website	QA/Test Days
Matrix	#test-day:fedoraproject.org
Mailing list	test

Can't make the date?
If you come to this page before or 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 at Bugzilla, 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 Fedora Test Day will focus on testing

Add Karmas to F41:https://bodhi.fedoraproject.org/updates/FEDORA-2024-50c8b12d3c
Add Karmas to F42:https://bodhi.fedoraproject.org/updates/FEDORA-2024-a3b076980b
Any regression noted in the new version

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. Use #podman or #fedora-test-day channels on libera chat. Alternatively, write on podman room In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.

Development - Mohan Boddu (mboddu), Lokesh Mandvekar (lsm5)
Quality Assurance - Adam Williamson (adamw),coremodule (coremodule), Sumantro Mukherjee (sumantrom)

Prerequisite for Test Day[edit]

A system (real or virtual) you can install Fedora 41, and not mind if it breaks
A simple way to get podman 5.3 would be "sudo dnf install podman --enablerepo=updates-testing".
Ensure running " rpm -qa podman" gives "podman-5.3.0~rc1-1.fc41.x86_64"

How to test?[edit]

Install Fedora[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 41 for this TestDay, or Fedora 41 container using Podman 5.3

Update your machine[edit]

Run the tests[edit]

Visit the result page and 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 Enter result button for the test.

Reporting bugs[edit]

If you have problems with any of the tests, report a bug to Bugzilla usually for the component podman. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Known issues[edit]

Test Results[edit]

Podman 5.3[edit]

User	Profile	Quadlet	Pasta Internal Container	References
aeperezt	f41	fail ^[1]	pass ^[2]	↑ Using the wiki page https://fedoraproject.org/wiki/QA:Testcase_pasta_quadlet and creating the file t1.container like ~/.config/containers/systemd/t1.container systemd does not find the file and do not start. Used systemctl edit --user --force --full t1.container to created container file with the content on the wiki and it added the file to the path $HOME/.config/systemd/user/t1.container.service stills failed Failed to start t1.container.service: Unit t1.container.service has a bad unit file setting. See user logs and 'systemctl --user status t1.container.service' for details. try modifing the t1.container but did not work. ↑ Works flawless
alciregi	Fedora 41 KVM	pass ^[1]	pass	↑ Yes, as is in the wiki page can't active (running) post-reboot
guiltydoggy		pass ^[1]	pass	↑ Test case says that the service should remain running, but it will run and then exit, leaving the status of the services as inactive (dead). However, the job does run successfully.
guiltydoggy	Fedora 41 Kinoite Podman version 5.3.0-rc2		pass
markr217	kvm	fail ^[1]	pass ^[2]	↑ t1.service starts but then logs show 'container died'. Status shows as inactive dead. ↑ Completed successfully.
orimanabu	MacBook Air M2, Fedora Asahi Remix 41, aarch64	pass ^[1]	pass	↑ If the status of the Quadlet service is expected to be “active (running)”, then wouldn't the value of ExecStart be better as `sh -c “ip addr && sleep infinity”` rather than just `ip addr`?
romangherta	F41 on Lenovo IdeaPad 5 14ARE05	pass ^[1]	pass	↑ The wiki page is a little bit confusing... to make sure the service is runing and active make sure you modify the service content to Exec=sh -c 'ip addr && sleep infinity'

Basic Test[edit]

User	Profile	Image Pull	Container	List Container	Remove Container	Inspect	Save and Load Images	References
adriend	X470 GAMING PRO + AMD Ryzen 5 2600X + AMD Radeon RX560	pass	pass ^[1]	pass	pass	pass	pass	↑ podman-5.3.0~rc1-1.fc41
aeperezt		pass ^[1]	pass ^[2]					↑ Run flawless ↑ run flawless
aeperezt	f41			pass ^[1]	pass ^[2]	pass ^[3] fail ^[4]	pass ^[5]	↑ Run flawless ↑ run flawless ↑ run flawless ↑ run flawless ↑ run flawless
alciregi	Fedora 41 KVM	pass	pass	pass	pass	pass
alciregi	Pinebook aarch64 F41	pass
carljmosca		pass	pass	pass	pass
dtma	F41,VM,x86_64	pass ^[1]	pass	pass	pass	pass	pass	↑ podman-5.3.0~rc2-1.fc41.x86_64
ersen	F41	pass	pass	pass	pass
geraldosimiao	F41 KDE at Acer Aspire V3-571 / i7-3632QM	pass	pass
guiltydoggy		pass	pass	pass	pass	pass
markr217	kvm	pass ^[1] pass ^[2]	pass ^[3]	pass ^[4]	pass ^[5]	pass ^[6]		↑ Completed successfully. ↑ Completed successfully. ↑ Completed successfully. ↑ Completed successfully. ↑ Completed successfully. ↑ Completed successfully.
mhough		pass
mhough	FC41 Intel_R_ Client Systems NUC8i7HVK, Intel® Core™ i7-8809G × 8, 32.0 GiB	pass	pass	pass	pass	pass
mhough	Intel_R_ Client Systems NUC8i7HVK, Intel® Core™ i7-8809G × 8, 32.0 GiB	pass
orimanabu	MacBook Air M2, Fedora Asahi Remix 41, aarch64	pass	pass	pass	pass	pass	pass
orimanabu	Sipeed Lichee Book 4A (riscv64), Debian trixie/sid, 5.10.113-zzz-sipeed-20240531+, Podman v5.3.0-rc2 (self build)	pass ^[1]	pass ^[2]	pass ^[3]	pass ^[4]	pass ^[5]	pass ^[6]	↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#image-pull ↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#container ↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#list-container ↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#remove-container ↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#inspect ↑ https://gist.github.com/orimanabu/a058b46f45e0ae2726e8654b86a0a5dd#save-and-load-images
romangherta	F41 on Lenovo IdeaPad 5 14ARE05	pass	pass	pass	pass	pass

Advanced[edit]

User	Profile	zstd	Composefs	System Shutdown	Virtiofs	References
aeperezt	f41	pass ^[1]	pass ^[2]	pass ^[3]	pass ^[4]	↑ All test worked as spected. ↑ running as expected ↑ Run flawless ↑ Working as expected
geraldosimiao	F41 KDE at Acer Aspire V3-571 / i7-3632QM			pass
orimanabu	MacBook Air M2, Fedora Asahi Remix 41, aarch64	pass	pass	pass	pass
romangherta	F41 on Lenovo IdeaPad 5 14ARE05	pass	pass	pass	pass

[1] Using the wiki page https://fedoraproject.org/wiki/QA:Testcase_pasta_quadlet and creating the file t1.container like ~/.config/containers/systemd/t1.container systemd does not find the file and do not start. Used systemctl edit --user --force --full t1.container to created container file with the content on the wiki and it added the file to the path $HOME/.config/systemd/user/t1.container.service stills failed Failed to start t1.container.service: Unit t1.container.service has a bad unit file setting. See user logs and 'systemctl --user status t1.container.service' for details. try modifing the t1.container but did not work.

[2] Works flawless

[3] Yes, as is in the wiki page can't active (running) post-reboot

[4] Test case says that the service should remain running, but it will run and then exit, leaving the status of the services as inactive (dead). However, the job does run successfully.

[5] t1.service starts but then logs show 'container died'. Status shows as inactive dead.

[6] Completed successfully.

[7] If the status of the Quadlet service is expected to be “active (running)”, then wouldn't the value of ExecStart be better as sh -c “ip addr && sleep infinity” rather than just ip addr?

[8] The wiki page is a little bit confusing... to make sure the service is runing and active make sure you modify the service content to Exec=sh -c 'ip addr && sleep infinity'

[9] -5.3.0~rc1-1.fc41

[10] Run flawless

[11] run flawless

[12] Run flawless

[13] run flawless

[14] run flawless

[15] run flawless

[16] run flawless

[17] -5.3.0~rc2-1.fc41.x86_64

[1]

[2]

[1]

[1]

[1]

[2]

[1]

[1]

[1]

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[1]

[1]

[2]

[3]

[4]

[5]

[6]

[1]

[2]

[3]

[4]

[5]

[6]

[1]

[2]

[3]

[4]

Search

Test Day:2024-11-01 Podman 5.3

Contents