Nicolas De loof
Nicolas De loof
@alexey-sh basically, compose supports none of the `deploy` attributes, which have been introduced for docker swarm
anything I can do to get this merged?
This issue will be obsolete after https://github.com/docker/compose/pull/13357, as status text isn't truncated anymore
Try to run same image with a plain `docker run..` command. If same error happens, then this is not a Docker Compose issue and this is not the right place...
Is this `db` service showing this error ? Please try `docker compose up db` to confirm
Closing as user didn't provided requested information. Feel free to open a new issue with more details if problem is still relevant
compose relies on `docker events`, and will detect `fail` container to `die` with exitCode != 0, so trigger application STOP _after_ exit code has been captured. The stop sequence sends...
The recommended approach to distinguish development environment (where you want port exposed) and other targets (CI/production) is to rely on override files. Typically, you could have a `compose.override.yaml` file with...
Closing as "not planned". Distinction between dev/CI/prod environment is better managed with an explicit override file
**update**: I replaced custom openapi code generator I used initialy to create this PR with a go-swagger fork, adapted to support openapi 3 schema (https://github.com/allons-y/openapi). Can hardly propose an upstream...