services.clamd-mailcow.depends_on.unbound-mailcow

DocFraggle

Hi,

I just updated my mailcow with the Mooctober update, now Docker won’t start due to this error:

services.clamd-mailcow.depends_on.unbound-mailcow Additional property restart is not allowed

Any ideas?

Regards, Christian

I had to remove these lines from docker-compose.yaml to get it working again:

https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml#L66
https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml#L308

@[deleted]

I had to remove these lines from docker-compose.yaml to get it working again:

https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml#L66
https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml#L308

@[deleted]

bitworxdigital

yep, had the same problem. removing the lines mentioned “solves” the problem for now…

Hindin-The-G

Same on my server, rolling back to a stabel version.

DocFraggle

@DerLinkman could you have a look at the dependencies?

DerLinkman

I think the reason for your issues is a older docker compose version.

I tested this things with the following version:

docker compose version
Docker Compose version v2.18.1

And everything works fine with that version.

DerLinkman

Jup it was the old version of compose. So i removed that from compose.yml.

See https://github.com/mailcow/mailcow-dockerized/releases/tag/2023-10a

DocFraggle

DerLinkman

I’m using 2.21 currently (Rocky Linux 8)

> docker compose version
Docker Compose version v2.21.0

Conan179

DerLinkman
o.O
cd /opt/mailcow-dockerized/ && /opt/mailcow-dockerized/update.sh
Detecting if your IP is listed on Spamhaus Bad ASN List…
Check completed! Your IP is clean
Checking internet connection… OK
Detecting which build your mailcow runs on…
You are receiving stable updates (master).
To change that run the update.sh Script one time with the –nightly parameter to switch to nightly builds.
Checking for newer update script…
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 11 (delta 4), reused 10 (delta 4), pack-reused 0
Unpacking objects: 100% (11/11), 7.12 KiB | 1.42 MiB/s, done.
From https://github.com/mailcow/mailcow-dockerized
5b8efeb2..a366494c master -> origin/master
f1c93fa3..99de302e staging -> origin/staging

[new tag] 2023-10a -> 2023-10a
Updated 0 paths from a843066d
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Great! Native IPv6 NAT is active.
Validating docker-compose stack configuration…
services.postfix-mailcow.depends_on.unbound-mailcow Additional property restart is not allowed

Oh no, something went wrong. Please check the error message above.

DerLinkman

DocFraggle Huh, then i did not get it actually why this is happening my version (the same now, i just updated to it) does not moan about this at all even with the old restart actions.

DocFraggle

Conan179

Yes, the problem is the docker compose validation before the Git checkout…

DerLinkman

Conan179 See: mailcow/mailcow-dockerized5456

Conan179

DerLinkman
um, what exactly do I have to change in the compose.yml?

DocFraggle

Conan179
Remove the to lines I posted in post #1

Ah, wait, they aren’t there anymore because the master branch was updated

[unknown]

These two lines:

https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L66
https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L308

[unknown]

These two lines:

https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L66
https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L308

These two lines:

https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L66
https://github.com/mailcow/mailcow-dockerized/blob/2023-10/docker-compose.yml#L308

DerLinkman

Do: git fetch && git checkout docker-compose.yml origin/master

Conan179

DerLinkman
us1@maschine:/opt/mailcow-dockerized# git fetch && git checkout docker-compose.yml origin/master
error: Pfadspezifikation »origin/master« stimmt mit keinen Git bekannten Dateien überein

DocFraggle

Conan179

It’s

git fetch && git checkout origin/master docker-compose.yml

DocFraggle

@DerLinkman I found the problem why your change didn’t work on my server despite of version 2.21.
Back in the days when I installed mailcow on my server and used the generate_config.sh script to generate my initial config, the docker-compose binary was installed, and so the variable DOCKER_COMPOSE_VERSION was set to “standalone”.
Then, I don’t remember when exactly, there was a change and docker compose was switched to the native binary. But the variable “DOCKER_COMPOSE_VERSION=standalone” was never updated in my mailcow.conf (I guess I didn’t see that in the patch notes) and the docker-compose binary is still present on my server. So up to today I always used the standalone version, which is 2.6.1 in my case, which of course doesn’t know about the restart change which was introduced in docker compose 2.17…

I suggest you all check which docker compose version is defined in your mailcow.conf 😉