Guillaume Lours
Guillaume Lours
As this behaviour is very specific to the development workflow, what do you think to manage that in a dedicated `development` section? @ndeloof started to [draft a PR](https://github.com/compose-spec/compose-spec/pull/253) about this...
Ok for the log/tmp and all the directories created by default by Rails initialiser 👍 @kochalex The purpose of the samples in this repository is it help people to bootstrap/see...
I'll transfer the issue to [the packaging repository](https://github.com/docker/docker-ce-packaging/) as this is not related to Compose
Users should add new elements to this kind of Map with the helper [`Add` function](https://github.com/compose-spec/compose-go/blob/4eed03fdaae1052e882e1923007b604278cfcee2/types/types.go#L485) that checks if the map is empty or not before adding a new value. Anyway...
Fixed by #281
Hello @rory-lamendola Compose v1 is end-of-life, the `cache_to` attribute was introduced in Compose v2 and won't be backported in Compose v1
FYI Docker Compose V1, the python version, reached end-of-life, please use Compose v2 instead and let us know if you still have the problem with this version. You can simply...
@KoditkarVedant I just restarted the CI, the `TestComposePull` test is still in error
What did you get if you try to run `docker --context mycontext pull an_image_from_compose_file` ?