Nicolas De loof
Nicolas De loof
this bug is caused by `shellwords.Parse` converting the configured string into a `ShellCommand`
@mmunz command should better not be used with such a long shell script. This will make maintenance painful and subject to bugs like this one. Better move this into a...
this is for sure an issue, but we don't have any simple solution here. docker-compose v1 is coded in python, and relies on python's `shlex` to parse the command attribute....
compose reconciliation logic only applies to services, so changes made to networks won't force those to be recreated. This is something we should fix.
Moving this issue to "Cloud Integration" repository
Moving issue to "Cloud Integration" repository, as this isn't related to Docker Compose
`env_file` and `environment` are **not** used for interpolation, but to set container's environment. `.env` file is the default source for interpolation, this is why you observe this behavior (can override...
indeed, as a yaml flavor of the equivalent `docker compose --env-file` flag. The main issue here is that both `docker run` and `docker compose` define this same flag, but for...
Implementation is correct but IMHO this issue will apply to way more places, not just `dns`. We miss a way to mark an entry in `compose.yaml` as "to be ignored...
@g-kartik nope, as volume name is unique we have no option to keep the existing one