Mailcow Docker Network

Ronny

Hi,

I want to use the clamav Container in another compose, so i try to Connect the mailcow container to my own.

When i do that my container is not reachable anymore.

Update: I put clamav in my nextcloud networ, that works. How can I create override yml so it is persistent?

My compose looks like this

    clamd-mailcow:
      image: ghcr.io/mailcow/clamd:1.70
      restart: always
      depends_on:
        unbound-mailcow:
          condition: service_healthy
      dns:
        - ${IPV4_NETWORK:-172.22.1}.254
      environment:
        - TZ=${TZ}
        - SKIP_CLAMD=${SKIP_CLAMD:-n}
      volumes:
        - ./data/conf/clamav/:/etc/clamav/:Z
        - clamd-db-vol-1:/var/lib/clamav
      networks:
        npmnet:
          aliases:
            - clamd

        mailcow-network:
          ipv4_address: 172.22.1.50
          aliases:
            - clamd

Greetings

esackbauer

Ronny I want to use the clamav Container in another compose, so i try to Connect the mailcow container to my own.

I don’t know if that container will then be either working properly in mailcow, or if mailcows specific configuration is unsuitable for your other compose.
Also you are then stuck to the releases of mailcow, and upgrading may or may not break your other compose.

Ronny

esackbauer

Sure, I will Update this by myself then. Watchtower is telling me what needs to be updated

Greetings

esackbauer

Updating mailcow with watchtower will not work, because versions are fixed. You have to use the update.sh script:
https://docs.mailcow.email/maintenance/update/

Ronny

esackbauer

I would do it manuelly. Do you know how to create override yml to add the network?

Greetings

esackbauer

Ronny
https://docs.mailcow.email/manual-guides/Docker/u_e-docker-cust_dockerfiles/

Ronny

esackbauer

Well when I do it like that it should also upgrade normally
docker-compose.override.yml

services:
    clamd-mailcow:
      networks:
        npmnet:
          aliases:
            - clamd

        mailcow-network:
          aliases:
            - clamd

networks:
  npmnet:
    external: true
  mailcow-network:
    driver: bridge
    driver_opts:
      com.docker.network.bridge.name: br-mailcow
    enable_ipv6: true
    ipam:
      driver: default
      config:
        - subnet: ${IPV4_NETWORK:-172.22.1}.0/24
        - subnet: ${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}