Using Docker version 28.0.4, build b8034c0 with the example docker-compose.yml gives the following warning:
WARN[0000] /tmp/tmp-mw/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
This is a bit disconcerting for new sysadmins. Removing the attribute without replacement would be ideal, if not prevented by WMF internal compatibility.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T393193 docker-compose.yml in standard package refers to absent DEVELOPERS.md | |||
| Resolved | Douginamug | T393183 Remove docker-compose.yml from MediaWiki archive releases | |||
| Resolved | Douginamug | T393171 Example `docker-compose.yml` gives warning about obsolete `version` attribute |
Can you please link to the file? I can't find it in mediawiki or mediawiki-docker.
I wrote some patches to get rid of "version": from Docker files a year or two ago. Here's one of them.
Sorry, the manifest I'm talking about is in Dockerhub: https://hub.docker.com/_/mediawiki/ which I believe is ultimately sourced from https://github.com/docker-library/docs/blob/master/mediawiki/README.md#-via-docker-compose-or-docker-stack-deploy
Yeah that looks like a duplicate of the tasks @Douginamug mentioned above. Could you update your build and see if this is still happening? I'll close this task as duplicate but please reopen if you still face this issue.
Looking more closely, this issue is technically different, since it refers to docker _hub_. I notice the example manifest on docker hub diverges significantly from the one contained in mediawiki/core — should this be so? Intuitively it would be nice if the mediawiki/core manifest propagated to hub.
FWIW, at a glance, it looks like the example docker-compose.yml displayed at Docker Hub is defined at https://github.com/docker-library/docs/blob/master/mediawiki/stack.yml. (I'm not personally sure whether/to what extent it should diverge from the manifest in mediawiki/core, though)
Actually the issue is the opposite (spoke with the reporter at the WMHackathon 2025 now) of what was reported here: T362669: docker-compose.yml `version` is now obsolete with Docker Desktop v4.29.0
The task linked above was to remove the version property from the yml file because it's obsolete but this task is about putting it back (it being absent is obsolete) which brings some confusion.
So maybe we should find a way to reconcile and decide whether to go forward with the property or not. NOTE: The docker community itself has deprecated [1] this feature and is no longer supported. This should probably be dropped from our latest images and people upgrade to the latest docker engine (?) maybe.
[1] ref. https://forums.docker.com/t/docker-compose-yml-version-is-obsolete/141313
@xSavitar I believe this issue refers to the exact same issue as T362669 and T364815, namely that the version attribute is obsolete and that docker compose as of v2.26 will give a warning. The only difference is that this issue refers to the docker-compose.yml on the docker hub example whereas the other two issues refer to the docker-compose.yml found in mediawiki/core.
Corrected PR link: https://github.com/docker-library/docs/pull/2564
Nice job with the patch :)