Music Assistant with HA in docker - network issues

Third party integrations
6

I know I’m painfully late to this conversation, but just wanted to say that now MA has no issues running in a Docker container even though my home network is very non-standard. My Docker server runs on my main network, and all my smart home stuff, including my RPi DAC streamer device running PiCorePlayer, is on another VLAN that has no visibility to the main network. Using host for the MA container was not an option for me. Below is my compose configuration. My br0.30 network is configured as a macvlan, and doing some research on these networks, it treats the Docker container as a full fledged machine and the typical port configuration for Docker containers is not needed, and is in fact ignored when using a macvlan network. I honestly expected this to be an uphill battle getting my non-standard configuration working, but it actually worked on the first try, and I think it’s because of the macvlan network.

services:
  music-assistant-server:
    image: ghcr.io/music-assistant/server:latest
    container_name: media-music_assistant_server
    restart: unless-stopped
    volumes:
      - ${DOCKER_STASH}/music-assistant-server/data:/data/
    # privileged caps (and security-opt) needed to mount smb folders within the container
    cap_add:
      - SYS_ADMIN
      - DAC_READ_SEARCH
    security_opt:
      - apparmor:unconfined
    environment:
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug)
      LOG_LEVEL: info
      TZ: ${TZ}
    networks:
      br0.30:
        ipv4_address: ${HAMA_IP}

networks:
  br0.30:
    external: true