back to labs
Containers: Start a Container at Boot with systemd
MediumRHCSA Prep15-20 minThe brief
A site container was started by hand with podman run. It works now, but after the next reboot it won't be running. Make it a systemd service that starts the container at boot, either with a unit from podman generate systemd or a Quadlet file in /etc/containers/systemd/. The brief is in /root/case/brief.txt. This lab runs a systemd stand-in that reads real unit and Quadlet files, so systemctl enable, daemon-reload and a reboot behave as they do on RHEL. Lab machines have no internet access, so the image is already in podman's local store, as if you had pulled it.
What you'll do
- Turn a running container into a systemd unit
- Enable a container service for boot
- Choose between podman generate systemd and Quadlet
Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.
