Open rybakit opened 5 years ago
+1 would love this, especially when deploying golang multi stage builds
Functionality maybe:
Also compose 3.4 introduces extension-fields.
And there is an incompatibility with healthcheck
.
official spec defines that the yaml healthcheck.start_period
is only supported in file version 3.4 https://docs.docker.com/compose/compose-file/compose-file-v3/#healthcheck
This means, that the field at the start of a docker-compose.yml file must write version: '3.4'
or greater. If 3.4 is not written, then official docker-compose
tool throws error
ERROR: The Compose file './xxxxx.yml' is invalid because:
services.xxxxxxx.healthcheck value Additional properties are not allowed ('start_period' was unexpected)
But ecs cli doesn't support writing 3.4
at the top. This means that it is not possible to declare the start_period
attribute in a docker-compose
file which is used across stages (local, LAN, AWS EC2, AWS ECS, etc.).
Unsupported Docker Compose version found: 3.8
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_CLI.html When will ecs-cli support minor versions like 3.8? I would like to common variable function which is introduced docker-compose 3.4+.
Is there a certain reason for not supporting minor versions? Do we have to wait until version 4 for being able to use common variables?
Summary
Currently,
ecs-cli
only supports major docker compose versions, like 2.0, 3.0. However, version 3.4 introduced multi-stage builds which allows building complex but efficient images within a singe Dockerfile. It would be greate ifecs-cli
could support this feature.Description
Which specific command was run?
Which version of the CLI you are using?
What platform are you using to run ECS CLI commands? (E.g. Linux, MacOSX, Windows)
Linux
Config files
Expected Behavior
The command succeeds without errors.
Observed Behavior
The command fails with: