Skip to content

Resolve env vars in docker-compose container names#101

Merged
jonathonbyrdziak merged 1 commit intomasterfrom
fix/docker-envvar-resolve
Mar 22, 2026
Merged

Resolve env vars in docker-compose container names#101
jonathonbyrdziak merged 1 commit intomasterfrom
fix/docker-envvar-resolve

Conversation

@jonathonbyrdziak
Copy link
Copy Markdown
Contributor

Summary

  • getContainerNamesFromDockerComposeFile() now resolves Docker-style env var patterns like ${CONTAINER_NAME:-ghostagent} to their actual values
  • Checks .env file in repo dir first, then system environment, then falls back to the default value after :-
  • Fixes status and health checks showing the literal ${CONTAINER_NAME:-ghostagent} string and always reporting containers as "not running"

Test plan

  • protocol status shows ghostagent instead of ${CONTAINER_NAME:-ghostagent}
  • Container running status correctly detected
  • Works with .env file overriding the default
  • Works with no .env file (uses default from :-)

🤖 Generated with Claude Code

getContainerNamesFromDockerComposeFile() now resolves Docker-style
env var patterns like ${CONTAINER_NAME:-ghostagent} to their default
values. Checks .env file in repo dir first, then system environment.

Fixes status/health checks showing literal '${CONTAINER_NAME:-ghostagent}'
and always reporting containers as not running.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jonathonbyrdziak jonathonbyrdziak merged commit 639e04e into master Mar 22, 2026
5 of 8 checks passed
@jonathonbyrdziak jonathonbyrdziak deleted the fix/docker-envvar-resolve branch March 22, 2026 03:56
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