(Created page with "{{QA/Test_Case |description=This test case ensures that Podman’s pasta integration allows stable rootless quadlet startup on boot, overcoming race conditions in network setup. |setup=Install Podman 5.3, ensure loginctl is configured for user lingering, and create a quadlet service file. |actions= Create a quadlet file at ~/.config/containers/systemd/t1.container with the following contents: <pre> [Container] Image=quay.io/libpod/testimage:20240123 Exec=ip addr [...") |
(fix the test case, quadlet file will be converted to a .service so we must use that for the systemctl commands. Also they cannot be enabled as these are generated files, the WantedBy is enough to cause it to be started at bot as quadlet creates the proper symlink) |
||
| Line 16: | Line 16: | ||
loginctl enable-linger $USER | loginctl enable-linger $USER | ||
Start the quadlet service and make sure it is working: | |||
systemctl --user | systemctl --user daemon-reload | ||
systemctl --user | systemctl --user start t1.service | ||
systemctl --user status t1.service | |||
Reboot the system: | Reboot the system: | ||
| Line 27: | Line 28: | ||
Verify the quadlet service status post-reboot: | Verify the quadlet service status post-reboot: | ||
systemctl --user status t1. | systemctl --user status t1.service | ||
|results= | |results= | ||
Latest revision as of 13:14, 1 November 2024
Description
This test case ensures that Podman’s pasta integration allows stable rootless quadlet startup on boot, overcoming race conditions in network setup.
Setup
Install Podman 5.3, ensure loginctl is configured for user lingering, and create a quadlet service file.
How to test
Create a quadlet file at ~/.config/containers/systemd/t1.container with the following contents:
[Container] Image=quay.io/libpod/testimage:20240123 Exec=ip addr [Install] WantedBy=default.target
Enable user lingering:
loginctl enable-linger $USER
Start the quadlet service and make sure it is working:
systemctl --user daemon-reload systemctl --user start t1.service systemctl --user status t1.service
Reboot the system:
sudo reboot
Verify the quadlet service status post-reboot:
systemctl --user status t1.service
Expected Results
The following must be true to consider this a successful test run: The quadlet service is “active (running)” post-reboot, indicating successful integration of pasta network dependencies for rootless startup.
Optional
Explore different quadlet service configurations with various networks to test pasta’s stability in additional network setups.