fix(install): always delete old hyperstack-mcp before creating new one#46
Merged
KailasMahavarkar merged 2 commits intomainfrom Apr 11, 2026
Merged
fix(install): always delete old hyperstack-mcp before creating new one#46KailasMahavarkar merged 2 commits intomainfrom
KailasMahavarkar merged 2 commits intomainfrom
Conversation
The MCP config references 'hyperstack-mcp' but users often have a differently-named container from a prior 'docker run' without --name. This is the #1 cause of 'tool not found' errors. - Add name mismatch repair script in Step 3 (before config) - Add auto-repair in Step 4 pre-check verification - Promote to #1 item in troubleshooting section
Existing containers cause 'docker run --name' to fail since the name is already in use. They also may run stale images or have leftover state. Add 'docker rm -f hyperstack-mcp 2>/dev/null' before container creation in both fresh install and upgrade paths.
KailasMahavarkar
added a commit
that referenced
this pull request
Apr 14, 2026
fix(install): always delete old hyperstack-mcp before creating new one
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Existing containers cause 'docker run --name' to fail since the name is already in use. They also may run stale images or have leftover state.
Add
docker rm -f hyperstack-mcp 2>/dev/nullbefore container creation in both fresh install and upgrade paths.