You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i start a pod using qublet, additional pause containers are created, one for every pod. What i red online is that they are there to keep network namespace alive if all other containers within the pod die.
If these are supposed to keep a pod network namespace alive, shouldnt they be in the pod?
Screenshot of the issue: the 3 top containers with suffix "-service" are outside of the pods. Pods with podman inspect show there are more containers inside (one being infra).
Used yaml which is started with systemd /etc/containers/systemd/vaultwarden.yaml:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When i start a pod using qublet, additional pause containers are created, one for every pod. What i red online is that they are there to keep network namespace alive if all other containers within the pod die.
If these are supposed to keep a pod network namespace alive, shouldnt they be in the pod?
Screenshot of the issue: the 3 top containers with suffix "-service" are outside of the pods. Pods with podman inspect show there are more containers inside (one being infra).
Used yaml which is started with systemd
/etc/containers/systemd/vaultwarden.yaml
:And systemd / qublet unit file
/etc/containers/systemd/vaultwarden.kube
:Details of
podman pod inspect e2c
Beta Was this translation helpful? Give feedback.
All reactions