Clément Désiles
a8545fc501
The previous Type=oneshot + RemainAfterExit=true pattern made systemd freeze pod units in 'active (exited)' as soon as 'podman play kube' returned, so crash-looping containers were invisible to 'systemctl --user --failed' and Restart=on-failure never fired. For every podman-pod role (immich, fdroid, ntfy, gitea, qfieldcloud, unifi, matrix, uptime_kuma): - switch units to Type=notify + NotifyAccess=all - run 'podman kube play --service-container=true' so the unit's main PID stays alive as long as the pod - use 'podman kube down' for ExecStop - add TimeoutStartSec=180 to cover slow first-boot image pulls Pod manifests: flip every container's restartPolicy from Always to Never. systemd is now the single owner of the restart loop: container exits -> pod dies -> service container dies -> unit fails -> Restart=on-failure restarts everything cleanly. With Always, podman retried internally and hid the failure from systemd. CLAUDE.md updated to document the new canonical template and the 'restartPolicy: Never' requirement.
39 lines
853 B
Django/Jinja
39 lines
853 B
Django/Jinja
---
|
|
apiVersion: v1
|
|
kind: Pod
|
|
metadata:
|
|
name: unifi
|
|
labels:
|
|
app: unifi
|
|
spec:
|
|
hostNetwork: true
|
|
containers:
|
|
- name: controller
|
|
image: {{ unifi_image }}:{{ unifi_version }}
|
|
env:
|
|
- name: TZ
|
|
value: "{{ unifi_timezone }}"
|
|
- name: SYSTEM_IP
|
|
value: "{{ unifi_bind_address }}"
|
|
- name: JVM_MAX_HEAP_SIZE
|
|
value: "{{ unifi_jvm_max_heap_size }}"
|
|
- name: UNIFI_STDOUT
|
|
value: "true"
|
|
volumeMounts:
|
|
- name: localtime
|
|
mountPath: /etc/localtime
|
|
readOnly: true
|
|
- name: unifi-data
|
|
mountPath: /unifi
|
|
restartPolicy: Never
|
|
|
|
volumes:
|
|
- name: localtime
|
|
hostPath:
|
|
path: /etc/localtime
|
|
type: File
|
|
- name: unifi-data
|
|
hostPath:
|
|
path: {{ unifi_data_dir }}
|
|
type: Directory
|