2 ms·
Docker compose development was compromised by the agenda of pushing people to use swarm. This is why v2 features like resource limits were moved under the depl
by Rapzid 6y ago
Docker compose development was compromised by the agenda of pushing people to use swarm.
This is why v2 features like resource limits were moved under the deploy: key and you have to use the special "--compatibility" flag to get them to work locally.
- justincormack 6y agoThis is no longer the case. Compose is an open spec and the v2 and v3 formats are being merged into a unified format (where you don't need version numbers). There are now multiple implementations (eg for ECS/Fargate and ACI), and implementations are being encouraged to support all the options.