Nicolas De loof

right, my bad, have been reading too fast. The issue here is that compose compares actual container state with desired state only based on `service.foo` yaml section, where volume is...

IMHO this is a bug: one-off containers with label `com.docker.compose.oneoff=True` must not have impact on the compose application status As UX, it would also be nice those can be filtered-out...

As swarm does not apply the compose specification, I wonder this is relevant to rely on swarm docs to define those attributes in the compose specification. Better keep them with...

Are you ok with https://github.com/compose-spec/compose-spec/commit/20ebf93c4fca53ab0628b27d4c707c81639a6890 or do you feel those attributes require better documentation ? The point here is that those are legacy from docker compose file v3, introduced for...

I wonder we could support bash array syntax ```yaml devices: ${DEVICES[*]} ``` about the .env file format to define an array, using `DEVICES =(xxx,yyy)` could have some side effect on...

@boguszj definitely not a "good first issue" to look into.

@Mugane you misunderstood how interpolation works in compose. This isn't just some yaml templating. Interpolation takes place _after_ yaml has been parsed > I should note that in addition, csv...

> Why then would specifying a .env file NOT load values from that .env file into the docker-compose.yml ? values are not loaded _into the yaml_ but into the compose...

Nice catch. Compose indeed check service configuration has changed (using a hash) to detect need to recreate, but doesn't check the networks or volumes mounts match the global project configuration.

Actually, while I expected we did, volumes don't get re-created on configuration change - this involves a risk to loose data, so would at least require an explicit flag or...