-
I have a collection of containers that are orchestrated with
I then have to run something like this to fix it:
It just recently (about a month ago), started doing this, so I'm not sure what happened. Here's one of my
Here's one of my Kubernetes style YAML files: apiVersion: v1
kind: Pod
metadata:
labels:
app: authelia-pod
name: authelia-pod
spec:
hostname: authelia-pod
securityContext:
seLinuxOptions:
type: spc_t
containers:
- name: authelia
image: ghcr.io/authelia/authelia:latest
imagePullPolicy: Never
#args:
#- --config
#- /config/configuration.yml
env:
- name: AUTHELIA_JWT_SECRET
value: REDACTED
- name: AUTHELIA_STORAGE_ENCRYPTION_KEY
value: REDACTED
- name: AUTHELIA_NOTIFIER_SMTP_PASSWORD
value: REDACTED
- name: AUTHELIA_IDENTITY_PROVIDERS_OIDC_HMAC_SECRET
value: REDACTED
- name: AUTHELIA_IDENTITY_PROVIDERS_OIDC_ISSUER_PRIVATE_KEY
value: REDACTED
- name: AUTHELIA_SESSION_SECRET
value: REDACTED
volumeMounts:
- mountPath: /config
name: authelia-config
- name: redis
image: docker.io/library/redis:latest
#args:
#- redis-server
volumeMounts:
- mountPath: /data
name: redis-data
volumes:
- name: redis-data
persistentVolumeClaim:
claimName: redis
- hostPath:
path: /home/cassidy/.config/containers/systemd/services/authelia/authelia
type: Directory
name: authelia-config |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
@mheon PTAL |
Beta Was this translation helpful? Give feedback.
-
@vrothberg I assume some sort of removal of the pod and associated containers from the Kube YAML should be happening on unit start? |
Beta Was this translation helpful? Give feedback.
The generated systemd units have a
ExecStart=/usr/bin/podman kube play --replace
(note the --replace). So to me it looks like the unit got shot down on stop (i.e.,ExecStopPost=/usr/bin/podman kube down
).Without a reproducer we cannot be sure but I think it makes sense to have
kube down
and--replace
remove "external" storage containers to account for such cases.