Just following setup at: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ However when I run docker-compose pull it fails on: `WARN[0000] The "WATCHDOG_NOTIFY_EMAIL" variable is not set. Defaulting to a blank string. 1 error(s) decoding: * error decoding 'Ports': Invalid ip address :: address ::: too many colons in address root@yuri:/websites/mailcow-dockerized# docker-compose -v` * error decoding 'Ports': Invalid ip address :: address ::: too many colons in address root@yuri:/websites/mailcow-dockerized# docker-compose -v"` versions are: Docker version 20.10.7, build 20.10.7-0ubuntu5~18.04.3 Docker Compose version v2.2.3 Now I assume it is complaining on - IPV6_NETWORK=${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64} However I'm unsure as there is no clear message to work from here, but that is the only place I find :: in the file I tried disabling IPv6 as well: https://mailcow.github.io/mailcow-dockerized-docs/firststeps-disable_ipv6/ Which did not help. Suggestions? Thanks, ERIC

docker compose> Invalid ip address :: address ::: too many colons

egandt

Just following setup at: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/
However when I run docker-compose pull it fails on:
`WARN[0000] The “WATCHDOG_NOTIFY_EMAIL” variable is not set. Defaulting to a blank string.
1 error(s) decoding:

error decoding ‘Ports’: Invalid ip address :: address ::: too many colons in address
root@yuri:/websites/mailcow-dockerized# docker-compose -v`

error decoding ‘Ports’: Invalid ip address :: address ::: too many colons in address
root@yuri:/websites/mailcow-dockerized# docker-compose -v"`

versions are:
Docker version 20.10.7, build 20.10.7-0ubuntu5₁₈.04.3
Docker Compose version v2.2.3

Now I assume it is complaining on

IPV6_NETWORK=${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}
However I’m unsure as there is no clear message to work from here, but that is the only place I find :: in the file
I tried disabling IPv6 as well: https://mailcow.github.io/mailcow-dockerized-docs/firststeps-disable_ipv6/
Which did not help.

Suggestions?

Thanks,
ERIC

egandt

I got past this by setting my bind ports for HTTP and HTTPS in mailcow.conf so that it looked like:

I did not want http exposed (blocked anyways by FW, so set it to localhost

`HTTP_PORT=4080
HTTP_BIND=127.0.0.1

HTTPS_PORT=4443
HTTPS_BIND=151.XXX.XXX.XXX`

Love when I can answer my own questions, hopefully it helps someone else
ERIC

MAGIC

Seems you didnt follow the install guide correctly. You are using docker-compose v2 which is not yet supported by mailcow due to changes in the network part

egandt

Actually I could not get it to start using docker-compose 1.3 (which is what I was using, had to go to 2.X before it worked and yes I had to make a few adjustments to networking for my setup, but so far it is working fine now in testing. Using 1.3 I had issues on every variable that was of the form ${XXX:-}, for example

`- REDIS_SLAVEOF_IP=${REDIS_SLAVEOF_IP:-}

REDIS_SLAVEOF_PORT=${REDIS_SLAVEOF_PORT:-}`

Would not work, upgrading 2.2.3 solved, though now I have some which setups that require 1.X and this using 2.X so not perfect.

ERIC