2024-03-21 Podman 5

Podman 5


Date	2024-03-21 to 2024-03-26
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 Week will focus on testing

Upgrade from 4.9 and lower to 5.0
Test ‘Podman save’ from 4.9 and ‘Podman load’ in 5.0
FCOS/Silverblue
Toolbx
Add Karmas to https://bodhi.fedoraproject.org/updates/FEDORA-2024-a267e93f8c

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 40, and not mind if it breaks
A simple way to get podman 5.0.0-1 would be "sudo dnf install podman --enablerepo=updates-testing".
Ensure running " rpm -qa podman" gives "podman-5.0.0-1.fc40.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 40 for this Test Week, or run a Fedora 39 and/or Fedora 40 container using Podman 5.

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[edit]

User	Profile	Save and Load Images	References
AngusVW	Operating System: Fedora Linux 40 (Workstation Edition Prerelease) Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Latitude 7490	pass ^[1] pass ^[2]	↑ The image was pulled and saved with podman 4.9.3 on Fedora Silverblue 39 by IMAGE ID. The image was transferred to and loaded on Fedora 40 by IMAGE ID. The image was verified to exist but did not retain the repository name. When a container was created with the image, there was a prompt to select repository, and the container was created successfully. ↑ The image was pulled and saved on Fedora Silverblue 39 by IMAGE ID. The image was transferred to and loaded on Fedora 40 by IMAGE ID. The image was verified to exist but did not retain the repository name. When a container was created with the image, there was a prompt to select repository, and the container was created successfully.
alciregi	Fedora 40 x86_64	pass
danniel	Fedora 40 x86_64	pass
davidel	Fedora 40 x86_64	pass
dtma	KVM,F40,x86_64	pass
ersen	Fedora 40 x86_64	pass
geraldosimiao	F40 KDE at Acer Aspire V3-571 / i7-3632QM	pass
hricky	Raspberry Pi 4, IoT 39.20231103.1, podman version 4.7.0 -> IoT 40.20240321.0, podman 5.0.0-rc2	pass
kronenpj	KVM Virtual Machine; Fedora 40	pass
nimdanitro	Fedora 40 x86_64	pass
noadcoco	Fedora Linux 40 WorkStation + 4Gb RAM + CPU: AMD E2-9000e RADEON + GPU: AMD ATI RADEON	pass
orimanabu	Fedora 40 aarch64	pass ^[1]	↑ Fedora Linux Asahi Remix on MacBook Air M2
plugs	Fedora 40 on aarch64	pass
pnemade	F40 Silverblue x86_64	pass
r0b0ty	KVM Virtual Machine; Fedora 40 x86_64	pass ^[1]	↑ Using Fedora-KDE-Live-x86_64-40_Beta-1.10.iso in Virtual Manager. Original image saved using Podman 4.9.3 and loaded in the VM using Podman 5.0.0. All expected results were observed.

Basic Test[edit]

User	Profile	Image Pull	Container	List Container	Remove Container	Inspect	References
AngusVW	Operating System: Fedora Linux 40 (Workstation Edition Prerelease) Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Latitude 7490	pass ^[1]	pass ^[2]	pass ^[3]	pass ^[4]	pass ^[5]	↑ The fedora:latest image was pulled successfully ↑ The container was started, accessed, exited, and was removed successfully. ↑ podman ps did not list the container podman ps --all listed the container with Status: Exited ↑ The container was listed with podman ps --all and removed succcessfully ↑ The container was identified and inspected by CONTAINER ID successfully.
alciregi	Fedora 40 x86_64	pass	pass	pass
alciregi	Oracle Cloud VM.Standard.A1.Flex	pass	pass	pass
danniel	Fedora 40 x86_64	pass	pass	pass	pass	pass
davidel	Fedora 40 x86_64	pass	pass	pass	pass	pass ^[1]	↑ I ran a container with the following command podman run -dt -p 8080:80/tcp docker.io/library/httpd on podman 4.9 on Fedora 39 and on podman 5 on Fedora 40 and the I compared podman inspect output 1. EntryPoint value is "" on 4.9 and it is null on 5 2. StopSignal is 28 on 4.9 and it is "SIGWINCH" on 5 3. NetworkMode is "slirp4netns" on 4.9 and "pasta" on 5 4. "PortBindings"."80/tcp"[0]."HostIp" is "" on 4.9 and "0.0.0.0" on 5 5. Ulimits are different 6. "Ports"."80/tcp"[0]."HostIp" is "" on 4.9 and "0.0.0.0" on 5 7. State has a nested Health object on 4.9 but not on 5
dtma	KVM,F40,x86_64	pass	pass	pass	pass	pass
ersen	Fedora 40 x86_64	pass	pass	pass
garrmcnu	Fedora Workstation 40 (Beta 1.10) on KVM	pass	pass	pass	pass	pass
hricky	Raspberry Pi 4, IoT 40.20240321.0, podman 5.0.0-rc2	pass	pass	pass	pass	pass
kronenpj	KVM Virtual Machine; Fedora 40	pass	pass	pass	pass	pass
nimdanitro	Fedora 40 x86_64	pass	pass	pass	pass	warn ^[1]	↑ Compared various images between podman 4.9 and podman5. Only noticable difference is that with Podman 5 the StopSignal is a string (e.g. "SIGTERM") and not numerical as before:
noadcoco	Fedora Linux 40 WorkStation + 4Gb RAM + CPU: AMD E2-9000e RADEON + GPU: AMD ATI RADEON	pass	pass	pass	pass	pass
orimanabu	Fedora 40 aarch64	pass ^[1]	pass ^[2]	pass ^[3]	pass ^[4]	pass ^[5]	↑ Fedora Linux Asahi Remix on MacBook Air M2 ↑ Fedora Linux Asahi Remix on MacBook Air M2 ↑ Fedora Linux Asahi Remix on MacBook Air M2 ↑ Fedora Linux Asahi Remix on MacBook Air M2 ↑ Fedora Linux Asahi Remix on MacBook Air M2
orimanabu	Fedora 40 aarch64 (Asahi Remix on MBA M2)	pass
plugs	Fedora 40 on aarch64	pass	pass	pass	pass fail	pass
pnemade	F40 Silverblue x86_64	pass
r0b0ty	KVM Virtual Machine; Fedora 40 x86_64	pass	pass	pass	pass	pass
vishalvvr	KVM,F40,x86_64	pass	pass	pass		pass

[1] The image was pulled and saved with podman 4.9.3 on Fedora Silverblue 39 by IMAGE ID. The image was transferred to and loaded on Fedora 40 by IMAGE ID. The image was verified to exist but did not retain the repository name. When a container was created with the image, there was a prompt to select repository, and the container was created successfully.

[2] The image was pulled and saved on Fedora Silverblue 39 by IMAGE ID. The image was transferred to and loaded on Fedora 40 by IMAGE ID. The image was verified to exist but did not retain the repository name. When a container was created with the image, there was a prompt to select repository, and the container was created successfully.

[3] Fedora Linux Asahi Remix on MacBook Air M2

[4] Using Fedora-KDE-Live-x86_64-40_Beta-1.10.iso in Virtual Manager. Original image saved using Podman 4.9.3 and loaded in the VM using Podman 5.0.0. All expected results were observed.

[5] The fedora:latest image was pulled successfully

[6] The container was started, accessed, exited, and was removed successfully.

[7] s did not list the container podman ps --all listed the container with Status: Exited

[8] The container was listed with podman ps --all and removed succcessfully

[9] The container was identified and inspected by CONTAINER ID successfully.

[10] I ran a container with the following command podman run -dt -p 8080:80/tcp docker.io/library/httpd on podman 4.9 on Fedora 39 and on podman 5 on Fedora 40 and the I compared podman inspect output 1. EntryPoint value is "" on 4.9 and it is null on 5 2. StopSignal is 28 on 4.9 and it is "SIGWINCH" on 5 3. NetworkMode is "slirp4netns" on 4.9 and "pasta" on 5 4. "PortBindings"."80/tcp"[0]."HostIp" is "" on 4.9 and "0.0.0.0" on 5 5. Ulimits are different 6. "Ports"."80/tcp"[0]."HostIp" is "" on 4.9 and "0.0.0.0" on 5 7. State has a nested Health object on 4.9 but not on 5

[11] Compared various images between podman 4.9 and podman5. Only noticable difference is that with Podman 5 the StopSignal is a string (e.g. "SIGTERM") and not numerical as before:

[12] Fedora Linux Asahi Remix on MacBook Air M2

[13] Fedora Linux Asahi Remix on MacBook Air M2

[14] Fedora Linux Asahi Remix on MacBook Air M2

[15] Fedora Linux Asahi Remix on MacBook Air M2

[16] Fedora Linux Asahi Remix on MacBook Air M2

[1]

[2]

[1]

[1]

[1]

[2]

[3]

[4]

[5]

[1]

[1]

[1]

[2]

[3]

[4]

[5]

Search

Test Day:2024-03-21 Podman 5

Contents