Skip to content

fix(scripts): find the running api container through compose - #189

Merged
davidamacey merged 1 commit into
mainfrom
fix/187-api-container-check
Oct 9, 2026
Merged

davidamacey merged 1 commit into
mainfrom
fix/187-api-container-check

Conversation

@davidamacey

Copy link
Copy Markdown
Owner

Closes #187

download.sh and export_paddleocr.sh matched the bare name api (and triton-server) against docker ps, but containers are named ${COMPOSE_PROJECT_NAME}-<service>, so the check never hit and the temporary-container branch always ran. Both now resolve the service through compose with an explicit project (dc ps -q <service>). export_paddleocr.sh gets a project-scoped dc() used for all its compose calls.

Tests: tests/installer/test_api_container_check.py (docker shim; shim gained a generic <service>_container fixture). 3 of 4 tests fail on the old code, all pass now.

Based on #186 (refactor/rename-api-service-62). Retarget to main if #186 merges first.

download.sh and export_paddleocr.sh matched the bare name 'api' against
docker ps, but the container is named ${COMPOSE_PROJECT_NAME}-api, so the
check never hit and the temporary-container branch always ran. Resolve the
service with 'dc ps -q' (explicit -p project) instead. export_paddleocr.sh
gains a project-scoped dc() and uses it for every compose call.

Closes #187
@davidamacey
davidamacey changed the base branch from refactor/rename-api-service-62 to main October 9, 2026 14:20
@davidamacey
davidamacey merged commit 40699e5 into main Oct 9, 2026
2 checks passed
@davidamacey
davidamacey deleted the fix/187-api-container-check branch October 9, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: scripts/lib/download.sh never finds the api container (matches ^api$ against <project>-api)

1 participant