Inconsistent container name between `lstk` (`localstack-aws`) and MCP (`localstack-main`)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #26 by @jhubbardsf — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, typescript
Research direction
No files or tests are named. Start by tracing the lstk first-run container setup and the MCP's default container lookup, then decide whether to standardize on one name or document the difference. Done means the container name is consistent for both paths, or the distinction is clearly documented.
Written by the indexing model from the issue text.
Description
When running lstk for the first time, it sets up a Docker container named localstack-aws. However, the MCP currently searches for a container named localstack-main by default.
This mismatch can be confusing for new users and makes onboarding harder. It would be helpful to standardize the container name between lstk and the MCP (e.g., both using either localstack-aws or localstack-main), or to document the difference clearly.
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 14
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 18
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from localstack/localstack-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
localstack/localstack-mcp-server#112 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
localstack/localstack-mcp-server#110 ·
Maintainers usually reply within 1 day
-
localstack-azure-client: .bicepparam files that use readEnvironmentVariable() can't be deployedOpen
Difficulty 3/5 1-2 days Newbie friendliness 64/100
localstack/localstack-mcp-server#111 ·
Maintainers usually reply within 1 day
-
Azure weekly suite failingMay be free again @HarshCasper claimed this 29 days ago, and no pull request is open. Open
localstack/localstack-mcp-server#83 · 1 assignee ·
Maintainers usually reply within 1 day
-
Deployer health check blocks deploys to remote/ephemeral instances (requires a local gateway)Possibly taken @missusk claimed this 65 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
localstack/localstack-mcp-server#70 ·
Maintainers usually reply within 1 day
All issues in localstack/localstack-mcp-server
Similar issues
-
ci-cd desktop size:low telemetry-improvement telemetry-round-1
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vfarcic/dot-agent-deck#2079 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
status:in-linear
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
n8n-io/n8n#43006 · 3 comments ·
Maintainers usually reply within 1 day
-
🔊 a11y
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
betagouv/mon-entreprise#4726 ·
Maintainers usually reply within 9 days