bug(docker): docker compose stack not seeding KV with configs #677

New issue

Closed

opened 2026-03-28 04:27:19 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:27:19 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2102
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2102
Original created: 2025-12-11T04:00:33Z

Describe the bug
the docker compose stack needs to seed configs in the KV for each service it brings up, it seems to be working in k8s but not in docker.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Imported from GitHub. Original GitHub issue: #2102 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2102 Original created: 2025-12-11T04:00:33Z --- **Describe the bug** the docker compose stack needs to seed configs in the KV for each service it brings up, it seems to be working in k8s but not in docker. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.