When i previously update mailcow (three days ago), I got a prompt whether I would like to enable IPv6 NAT, i rejected this option because I disabled IPv6 completely using this guide:
After I run update.sh today i get error and mailcow is not running with error “Service ipv6nat-mailcow has neither an image nor a build context specified”. Please help.
Today error:
root@smtp:/opt/mailcow-dockerized# ./update.sh
Checking internet connection... OK
Checking for newer update script...
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...
WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string.
ERROR: The Compose file is invalid because:
Service ipv6nat-mailcow has neither an image nor a build context specified. At least one must be provided.
Rejected option:
root@smtp:/opt/mailcow-dockerized# ./update.sh
Checking internet connection... OK
Checking for newer update script...
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Native IPv6 implementation available.
This will enable experimental features in the Docker daemon and configure Docker to do the IPv6 NATing instead of ipv6nat-mailcow.
!!! This step is recommended !!!
mailcow will try to roll back the changes if starting Docker fails after modifying the daemon.json configuration file.
Should we try to enable the native IPv6 implementation in Docker now (recommended)? [y/N] N
OK, skipping this step.