fix(services): remove Quadlet files in stopped state #18

Merged

rohrschacht merged 3 commits from fix/stopped-remove-quadlets into main

2026-06-18 20:00:14 +00:00

forgejo-hermes-bot commented

2026-06-18 19:32:44 +00:00

Collaborator

Problem

After a server reboot, services with state: stopped came back online. Quadlet files were still in ~/.config/containers/systemd/ so Podmans systemd generator recreated the units on boot.

Fix

Skip Quadlet deployment for stopped
Remove Quadlet directory after stopping the service
Daemon-reload so systemd picks up the change

Everything else (user, btrfs, secrets, linger, traefik route) stays intact for quick re-activation.

## Problem After a server reboot, services with state: stopped came back online. Quadlet files were still in ~/.config/containers/systemd/ so Podmans systemd generator recreated the units on boot. ## Fix 1. Skip Quadlet deployment for stopped 2. Remove Quadlet directory after stopping the service 3. Daemon-reload so systemd picks up the change Everything else (user, btrfs, secrets, linger, traefik route) stays intact for quick re-activation.

forgejo-hermes-bot added 1 commit

2026-06-18 19:32:44 +00:00

fix(services): remove Quadlet files in stopped state to prevent auto-start 3895d70008

When state=stopped, Quadlet files were still deployed to
~/.config/containers/systemd/. After a server reboot, Podman's
systemd generator would re-create service units from these files,
causing stopped services to come back online.

Fix: skip Quadlet deployment for stopped, remove the Quadlet
directory after stopping the service, and daemon-reload so systemd
picks up the change.

forgejo-hermes-bot added 1 commit

2026-06-18 19:35:57 +00:00

fix(services): add user-existence guard to Quadlet removal 3d7338733c

The directory removal task ran unconditionally for state=stopped,
inconsistent with the daemon-reload task and the file's conventions.
Now both tasks require service_user_exists.rc == 0.

rohrschacht added 1 commit

2026-06-18 19:55:29 +00:00