How does one benefit from this change? With the latest Docker Desktop 4.25.2 (129061), I get configs.fpm Additional property content is not allowed.

configs.fpm Additional property content is not allowed.

I also tried this since it's published on the docs (configs top-level page, service configs attribute) and there is no min version description, so I assumed it was already available at some point.

I looked through the release notes and found nothing (not too fun with fairly generic keywords configs / content).

Then I tried to track down the source from the docs:

• There is no direct link for contributions on the rendered docs page, but it takes you to docker/docs repo.
• While some of the compose docs are there, this particular one was missing. Searched the repo and found hugo config ref.
• Now at compose-spec/compose-spec, found the docs page content and git blame to find out it was merged in Nov 7th here.
  • compose-go 1.20.1 (Nov 14th) released with the feature.
  • docker/compose upgraded to that dep on the same day. Then released v2.23.1 on Nov 16th.
    • The release notes don't mention the feature, nor does the Docker Compose docs release notes page.

That was a bit of a mission 😅 Didn't realize the feature was that new. I'm on v2.21.0 (Aug 30th).

I was on 4.23.0 (120376), but now also upgraded to the latest version is 4.25.2 (129061), but unfortunately that's not new enough 😆

TL;DR

How does one benefit from this change?

Docker Desktop 4.25.0 (released Oct 26th) provides Docker Compose 2.23.0 (docker compose version).

While 4.25.2 (Nov 21st) probably could have bumped the compose version, we'll probably have to wait a little bit longer for a new release to handle that.

@ndeloof

I would like to suggest upgrading compose specification version for changes like this one.

Just now I've ran into this situation:

• I write docker-compose.yml according to official docs
• I specify the latest available version: "3.8"
• docker compose does not complain about incompatibility with this version
• And yet I get an error Additional property content is not allowed

That is confusing.

I specify the latest available version: "3.8"

version is obsolete with compose-spec, it is ignored. Compose spec isn't versioned by design. The compose (tool) version you're using will let you know it can't parse your compose file if you use a recent addition.

docker compose does not complain about incompatibility with this version
And yet I get an error Additional property content is not allowed

This is exactly what "complain about incompatibility" is about. Maybe we should add "please upgrade docker compose" to this message.

@ndeloof

Unfortunately, there is no way to distinguish between "please upgrade docker compose" and "you mistyped a keyword or used it on incorrect nesting level".

version is obsolete with compose-spec, it is ignored.

That is sad 😢

Look at terraform and terraform providers, for example. Each version explicitly has it's own specification. As long as you follow that specification for selected version - you will not run into compatibility issues.