Nicolas De loof
Nicolas De loof
Docker Compose is not involved on system reboot, it _just_ asks engine to create containers by API, then Docker engine is in charge. According to your description, container is well...
Such an issue should be reported on github.com/moby/moby
> My guess is that depends_on containers still expose their service ports indeed. "one-off" container started by `run` command doesn't get ports exposed by default, as the `run` command is...
closing issue as "work as designed"
this is slightly different but close to https://github.com/docker/compose/issues/9181
> every developer need to check if we have some new envs You should declare variables in your compose.yaml with either a default value or error: ```yaml value: ${VAR:?must declare...
The root cause is probably we use the `mount` API in compose while `docker run -v` uses the (legacy) `bind` API. Can you try your reproduction scenario but replace `-v...
while not strictly required, I think we should use this opportunity while revisiting this command to add support for app_protocol and port name (https://github.com/compose-spec/compose-spec/blob/master/05-services.md#long-syntax-3)
`--index` is used to select service replica, already implemented in `backend.Port` calling `getSpecifiedContainer` Adding support for app_protocol would not be that simple, as such metadata only exists in compose model,...
This doesn't seem to be a compose issue: You should be able to get the same behavior with a plain `docker buildx build ...` command. If confirmed, please report on...