Nicolas De loof
Nicolas De loof
While resolution of #11867 is not trivial, I don't think we need such a new attribute for now. Mounting a remote path requires this one to be declared absolute, as...
On reboot, docker engine is the only one responsible to recreate/restart containers. AFAICT it doesn't manages precedence for containers and as such can produce conflicts, typically using a random IP...
Example request for such feature: https://github.com/docker/compose/issues/4081#issuecomment-1937787722 I 100% agree not being totally confident with such a non-portable feature
Let's close this one as lack of portability is challenging here
Oh nice, didn't know this fork exists. I tried migrating to goccy/go-yaml but this has significant impact
Can you please check same issue applies to `docker buildx bake -f compose.yaml` ?
ok, so this issue also applies to Bake, cc @crazy-max
We just introduced some additional diagnostic for git remote resources. Please clone this repo, run `make install` to get compose built from sources, then run your command again with `--verbose`...
@focdanisch thanks for sharing your workaround Sounds weird you get this error, as [email protected] is a valid SSH url (which is somehow flexible): ``` $ git ls-remote --exit-code [email protected]:docker/compose.git main...
This has been fixed by https://github.com/compose-spec/compose-go/commit/d3fd7d94aa317d62651db19be469c39e06f9c66d