Repository navigation
Validate Docker Compose configurations without starting containers - #7
Merged
Merged
Conversation
cheshi-mantu
self-requested a review
October 5, 2026 09:08
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
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.
Add a lightweight GitHub Actions check for all five Docker Compose configurations on pushes to
main, pull requests, and manual runs. Restricting push checks tomainavoids duplicate push and pull request runs for feature branches. Each file is validated withdocker compose config --quietusing its matchingenv-example, so invalid YAML or Compose models fail CI without pulling images or starting containers. The workflow uses read-only repository permissions, and the README includes a local validation command.Verification
bash -n.git diff --checkpassed.versionfield and unsetTLS_ENDPOINTSremain non-blocking.