-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update compose & run v2 of compose #9
Comments
For now, I'll just copy/paste my base config and edit out the port / volume bindings, but this would be ideal |
@strazto i'll take a look at all your suggestions in the next couple of weeks. But busy due to moving house but will get to when I can. |
GitHub made a breaking change on July 29th that rolled out from then until Aug 2, removing Compose v1 (docker-compose). (I believe this is what is causing issue #12 that was submitted today) Would you be open to have someone submit a PR? |
The current version of
docker-compose
is 0.23.5 :docker-compose-action/package.json
Line 18 in cf2e51f
Nevermind, it was actually the docker-compose binary on my runner
This version only supports the
docker-compose
v1
spec.The latest version of the npm docker-compose supports
v2
, since v0.24.0The compose spec added compose-spec/compose-spec#340 a yaml tag for resetting values in an override, for example
This is useful in CI, as I want to use my compose stack to run e2e tests, and disable portforwarding + persistence so I can run multiple compose stacks in parallel on the same runner, ie:
Note that in the above, I disabled concurrency within the same branch, but the workflow may run concurrently for different branches.
Currently, I get the following error:
I believe that using (or allowing) the v2 bindings may allow us to use new feature from the spec
Update - This can run
docker-compose
v2, however, the machine running this needs to aliasdocker-compose
to the plugin binary.A good enough way is to symlink it, https://stackoverflow.com/a/76909275/9238801
The text was updated successfully, but these errors were encountered: