docker-compose.yml: version is obsolete

[bersierj]

Contribution guidelines

• I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
• ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• ... I have understood that answers are voluntary and community-driven, and not commercial support.
• ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

With docker version 25.05 the version 2.1 in docker-compose.yml will be obsolete

Logs:

docker-compose.yml: `version` is obsolete

Steps to reproduce:

N/A

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

rocky linux 9

Server/VM specifications:

12GB/4 Core

Is Apparmor, SELinux or similar active?

yes

Virtualization technology:

kvm

Docker version:

25.0.5

docker-compose version or docker compose version:

v2.25.0

mailcow version:

2024-02

Reverse proxy:

Nginx

Logs of git diff:

N/A

Logs of iptables -L -vn:

N/A

Logs of ip6tables -L -vn:

N/A

Logs of iptables -L -vn -t nat:

N/A

Logs of ip6tables -L -vn -t nat:

N/A

DNS check:

N/A

[nabeeltahir785]

Please remove the version line from the docker-compose.yml file and verify that everything still works correctly on your end. Docker has made this line obsolete, which is likely the reason you're facing this issue

[conjunrad]

@nabeeltahir785 from which version of docker this line obsolete?

[bersierj]

If line is removed the warning go away.
the warning start with version 25.05

[Cl-Chris]

Compose doesn't use version to select an exact schema to validate the Compose file. See https://github.com/compose-spec/compose-spec/blob/master/04-version-and-name.md
So removing the first line version: '2.1' at the beginning of docker-compose.yml and docker-compose.override.yml (if exist) solve the problem.
This not specific to MailCow.

[damianszczepanik]

Is there any way to ignore this particular warning as long as I upgrade all docker-compose.yml files? Any flag for that?

[bersierj]

Is there any way to ignore this particular warning as long as I upgrade all docker-compose.yml files? Any flag for that?

Yes you can comment out the line or remove the line

[MAGICCC]

Seems we can remove this @DerLinkman. Seeing on https://docs.docker.com/compose/compose-file/04-version-and-name/#version-top-level-element-optional it's optional (now).

[abferm]

Some of my compose files need to remain compatible with older versions of docker/docker-compose. Is there any way to silence the warning without modifying the compose files?

[caoliang1918]

may be this issues can help you, jasonacox/Powerwall-Dashboard#453 (comment)

[melroy89]

@nabeeltahir785 from which version of docker this line obsolete?

version: "x.x.x" 

[elnath78]

@Cl-Chris

Compose doesn't use version to select an exact schema to validate the Compose file. See https://github.com/compose-spec/compose-spec/blob/master/04-version-and-name.md So removing the first line version: '2.1' at the beginning of docker-compose.yml and docker-compose.override.yml (if exist) solve the problem. This not specific to MailCow.

Why the examples still have the Version lines then? Also on Gitpod is not giving this problem.