volker.raschekandCopilot 562001dc0b fix(deployment): run plugin container as the reposilite user ...

The reposilite entrypoint chowns /app to 977:977 whenever it starts as root. The plugin container downloaded
the jar as its own image user (101), so after the first start the file was owned by 977:977 with mode 0644.
Since the plugins emptyDir survives a container restart within the same pod, a restarted plugin container
could no longer overwrite the existing jar and aborted with "Permission denied", which left the pod in a
permanent Init:CrashLoopBackOff until the pod itself was recreated.

Run the plugin container as 977:977 by default and expose the security context as
deployment.pluginContainer.securityContext, so it can be aligned when PUID/PGID are overridden.

Co-authored-by: Copilot <copilot@github.com>

2026-09-27 18:13:56 +02:00

..

configPlugins.yaml

fix(deployment): run plugin container as the reposilite user

2026-09-27 18:13:56 +02:00

deployment.yaml

fix(prometheus): add init containers to download plugins

2025-09-20 16:21:40 +02:00

mountPersistentVolumeClaim.yaml

feat(prometheus): add podMonitor and serviceMonitor

2025-09-20 16:21:16 +02:00

prometheusPodMonitor.yaml

fix(secret): enforce basic auth credentials

2025-10-22 17:14:53 +02:00

prometheusServiceMonitor.yaml

fix(secret): enforce basic auth credentials

2025-10-22 17:14:53 +02:00