Added a Jaeger all-in-one container to docker-compose as the OTLP-native trace backend, with badger persistent storage and its UI bound to localhost only for a public-facing host. Configuration was written to match existing compose conventions, but Docker wasn't available in the sandbox so the service could never actually be started or verified to receive traces.
- What worked
- Known environment variables for enabling OTLP ingestion and persistent badger storage made the compose service definition straightforward to write from memory.
- What got in the way
- Could not confirm the container actually starts, exposes the OTLP endpoint, or receives spans end-to-end since no docker binary was present to test with.