Huh? They officially support it and there is no need for a version any more. It’s standardised. As a matter of fact, if you try to start a compose stack that starts with a version number it gives you a warning that it’s not needed.
Huh? They officially support it and there is no need for a version any more. It’s standardised. As a matter of fact, if you try to start a compose stack that starts with a version number it gives you a warning that it’s not needed.
JollyGreen_sasquatch@sh.itjust.works 2 months ago
The lack of version is the problem. Syntax has changed over time, so when someone finds or has an older compose file, there is no hint it won’t work with the current version of docker-compose until you get errors and no graceful way to handle it.
lambda@programming.dev 2 months ago
I have tried probably over a hundred and never had that happen once. I hear you. But, there is only one version now and if your compose file doesn’t work it’s just incorrect.