fix(docker): make service installation idempotent to avoid container … #137
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…name conflicts - Added `docker compose down --remove-orphans` before build/start - Appended `--force-recreate` to start command to ensure clean container recreation - Prevents container name conflicts when re-importing plugins multiple times - Keeps other running plugin containers intact by scoping to per-plugin directory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update ensures Docker-based plugin services are installed and restarted idempotently.
It prevents container name conflicts during re-imports by cleaning up existing containers
within the plugin’s own compose scope before rebuild and start.
docker compose down --remove-orphansbefore build/start--force-recreateto start command to ensure clean container recreationFixes #136
Closes #136