Laura Brehm

Thanks for making the proposal @nickjj! I think speaking on behalf of the Docker Compose maintainers, we're alright with putting addressing https://github.com/docker/compose/issues/9795 on hold until a discussion can be had...

Hi @stumpylog, I'm having trouble replicating this in `v2.11.0`. Could you share a Compose file that reproduces this, along with how you're creating the external network and any other relevant...

@ulyssessouza looks like this was introduced in https://github.com/docker/compose/pull/9817. Can you take a look?

@sphinxc0re in the meantime, as mentioned by @niklas-rittmann, you can use `DOCKER_HOST=ssh:// docker compose [xxx]` to circumvent this issue.

Hi @njalooo, thanks for the report. Can you provide some additional information, such as if this bug is new (did this work in previous compose versions?) and whether this works...

@thaJeztah this looks like a https://github.com/moby/moby (or maybe runc) issue to me, wdyt?

We can either keep it as is, or change the `test-coverage` Dockerfile target to run some other step without the e2e, it doesn't make sense to run the end-to-end tests...

For comparison: ```Go t.Run("abort-on-container-exit", func(t *testing.T) { res := c.RunDockerComposeCmdNoCheck(t, "-f", "./fixtures/cascade-stop-test/compose.yaml", "--project-name", projectName, "up", "--abort-on-container-exit") res.Assert(t, icmd.Expected{ExitCode: 1, Out: `should_fail-1 exited with code 1`}) res.Assert(t, icmd.Expected{ExitCode: 1, Out: `Aborting...

Thanks! :) I removed `cascade_stop_test.go` which was replaced by `stop.feature` and `compose_down_test.go` which was replaced by `down.feature`, and their corresponding fixtures, so the comparison is clearer in the PR.

From [here](https://github.com/docker/compose/pull/9824#discussion_r978066244), moved the new tests into a new `e2e` module to separate out test dependencies.