3 ms·

FWIW the standard now says the file should be called "compose.yaml"; "docker-compose.yaml" is supported but deprecated

krick 4y ago
Ambitious decision. As if docket-compose is the only tool that uses the word compose, and there is no other extremely common tool, that uses for configuration, for instance, files like composer.json and composer.lock.
- guffins 4y ago
  I’m on my phone and haven’t double checked this, but from my understanding, I believe it’s part of an effort to encourage compatibility with other tools like podman. The ambiguity is somewhat intentional, as an active decision to separate the implementation name from the configuration standard.
  - przemo_li 4y ago
    composer.json is from PHP. Config file for package manage (almost universal). So it will be even bigger pain in the keyboard to write them :(
Too 4y ago
Equally confusing and often misunderstood is that the latest version of a compose file should not have a version field at all! It is a blend of v2, v3 and any newly added attributes (v3 some times supported less than v2), that is now called the compose spec. Implementations are supposed to do feature detection based on what attributes are used in the file. Make sure your docker compose is new enough, otherwise it thinks absence of version field means v1!
- throwawaaarrgh 4y ago
  Yeah I was gonna complain about this but honestly I don't even know what the hell they're doing with the version field anymore. I suspect it's because they want to force you to upgrade because otherwise they may have to support legacy longer.
nickjj 4y ago
That is a big change. After June 2023 Docker Compose v1 will officially no longer be supported. I probably won't switch right then and there to the new filename but that is at least one ball moving in the right direction to switch over to the new file. The other problem is more of a human one. There's 7+ years worth of blog posts, videos and documentation referencing docker-compose.yml. Having all of those become invalid is a big price to pay when onboarding new folks to Docker. When learning something new, it stinks when you find conflicting or different information all over the place. Long story short, I will switch to using it but it's going to take time.

Ambitious decision. As if docket-compose is the only tool that uses the word compose, and there is no other extremely common tool, that uses for configuration, for instance, files like composer.json and composer.lock.

guffins 4y ago
I’m on my phone and haven’t double checked this, but from my understanding, I believe it’s part of an effort to encourage compatibility with other tools like podman. The ambiguity is somewhat intentional, as an active decision to separate the implementation name from the configuration standard.
- przemo_li 4y ago
  composer.json is from PHP. Config file for package manage (almost universal). So it will be even bigger pain in the keyboard to write them :(

Too 4y ago

Equally confusing and often misunderstood is that the latest version of a compose file should not have a version field at all! It is a blend of v2, v3 and any newly added attributes (v3 some times supported less than v2), that is now called the compose spec. Implementations are supposed to do feature detection based on what attributes are used in the file. Make sure your docker compose is new enough, otherwise it thinks absence of version field means v1!

throwawaaarrgh 4y ago
Yeah I was gonna complain about this but honestly I don't even know what the hell they're doing with the version field anymore. I suspect it's because they want to force you to upgrade because otherwise they may have to support legacy longer.

nickjj 4y ago

That is a big change. After June 2023 Docker Compose v1 will officially no longer be supported. I probably won't switch right then and there to the new filename but that is at least one ball moving in the right direction to switch over to the new file. The other problem is more of a human one. There's 7+ years worth of blog posts, videos and documentation referencing docker-compose.yml. Having all of those become invalid is a big price to pay when onboarding new folks to Docker. When learning something new, it stinks when you find conflicting or different information all over the place. Long story short, I will switch to using it but it's going to take time.