From Fedora Project Wiki

Revision as of 10:46, 27 October 2024 by Sumantrom (talk | contribs) (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 [...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

Enable and start the quadlet service:

   systemctl --user enable t1.container
   systemctl --user start t1.container

Reboot the system:

   sudo reboot

Verify the quadlet service status post-reboot:

   systemctl --user status t1.container

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.