Skip to content

ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.

Fix Jaeger exiting at start on a fresh volume

Juan Denis4730afa031b3
diff --git a/backend/templates/jaeger.yaml b/backend/templates/jaeger.yaml
index e9a91cb0..f191c8d6 100644
--- a/backend/templates/jaeger.yaml
+++ b/backend/templates/jaeger.yaml
@@ -22,6 +22,15 @@ variables:
default: "14268"
hidden: true
+# What the OpenTelemetry Collector gets through `fromService` (Attach → Traces
+# on the collector), over the shared service network. Jaeger accepts OTLP on
+# 4317/4318 by default.
+connection:
+ port: 4317
+ properties:
+ otlpGrpc: "{host}:4317"
+ url: "http://{host}:16686"
+
ports:
- port: 16686
protocol: tcp
@@ -48,6 +57,11 @@ compose:
image: jaegertracing/all-in-one:${VERSION:-1.52}
container_name: ${APP_NAME}
restart: unless-stopped
+ # The image runs as an unprivileged user, and a fresh named volume at
+ # /badger is root-owned, so badger could not create its key/data
+ # directories and Jaeger exited at start ("mkdir /badger/key:
+ # permission denied"). The volume is private to this container.
+ user: "0"
environment:
- SPAN_STORAGE_TYPE=badger
- BADGER_EPHEMERAL=false