hero_services: Docker deployment broken after service config restructuring #49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The recent merge of
development_kristofintodevelopmentrestructured service configs but left the Docker deployment pipeline broken. This is part of the larger hero_proc transition (#50).What's broken
Profiles not copied to Docker image —
profiles/directory exists in repo butdocker/build-local.shnever copies it todist/. The entrypoint runshero_services_server run --profile userbut the binary can't find profiles.build-local.sh validation — still expects
services/user/(old layout). Configs are now flat inservices/.Binary name mismatch — service TOMLs reference new names (
_openrpc/_http) but most repos still produce old names (_server/_ui). This is expected during the transition per #50.Specific files
docker/build-local.sh— needs to copyprofiles/todist/, fix validation for flat layoutdocker/entrypoint.sh— needs binary symlinks (_server→_openrpc,_ui→_http) as a bridgeDockerfile.pack— needsCOPY profiles/lineContext
Per #50, the architecture is transitioning to:
--startflagThis fix bridges the current state until the full transition completes.
Impact
Progress: compile fixes pushed to development
All 18 services now compile (0 failures). Fixes pushed across 5 repos:
What works
SKIP_WASM=1 make distWhat remains: hero_proc migration
The Docker deployment still uses zinit as the process supervisor, which causes startup race conditions (services exhaust retry limits before dependencies stabilize). Per #50, hero_proc replaces zinit entirely. Next steps:
This is tracked under #50. Keeping this issue open until Docker deployment is fully functional with hero_proc.
hero_proc migration complete — runtime working
Pushed to development:
bd14ea1— feat: replace zinit with hero_proc as process manager (#50)What was done
Test results
Remaining
5 services still use old CLI pattern (no serve subcommand) — tracked in #52.
Signed-off-by: mik-tf
Docker deployment working — 20/21 services running, all smoke tests pass. Fixed in P0 and verified through P1-P2 work.
Signed-off-by: mik-tf