Skip to content

docs: run one-off docker.sh modes beside the running client; F19 - #662

Merged
Ultimate-Storm merged 1 commit into
mainfrom
docs/one-off-modes-beside-client
Oct 16, 2026
Merged

Ultimate-Storm merged 1 commit into
mainfrom
docs/one-off-modes-beside-client

Conversation

@Ultimate-Storm

Copy link
Copy Markdown
Contributor

Found while verifying 1.9.3 with real TUD_1/TUD_2 kits on the production coordinator: --preflight_check, --run_script (the D2.5 Greek step), --local_training, --external_validation and --dummy_training all start their container under the client's name (--name=$CONTAINER_NAME in the common docker options), so docker refuses while the client runs:

docker: Error response from daemon: Conflict. The container name "/odelia_swarm_client_TUD_1_ba35d9ed" is already in use

The existing --container_name flag fixes it without a kit change (verified: preflight and the full D2.5 Greek script ran beside the running client). This PR adds it to the BreastDivider site guide, the run plan and the D2.5 script header, and documents the error as F19. A later kit should name one-off containers automatically (issue to follow).

🤖 Generated with Claude Code

…ner_name); F19

Found while verifying 1.9.3 with real kits: --preflight_check, --run_script and the other one-off
modes start under the client's container name and docker refuses while the client runs. The site
guides now add --container_name; F19 documents the error and the fix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Ultimate-Storm
Ultimate-Storm merged commit 1be5aa8 into main Oct 16, 2026
7 checks passed
@Ultimate-Storm
Ultimate-Storm deleted the docs/one-off-modes-beside-client branch October 16, 2026 14:02
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.

1 participant