Config path in Docker not working?

[rtangwai 1]

I have the strangest problem with Emby in Docker on Ubuntu 22.04.

When I set the /config path in volumes to a local path on the host like /usr/share/emby it doesn't write to it but Emby is accessible on port 8096.

When I set the /config path to a mapped shared folder it does write the config files, but then it is *NOT* accessible on port 8096.

The path is the *ONLY* thing I changed - any ideas why it would do something so weird?

See my docker-compose.yml below:

version: "2.3"
services:
  emby:
    image: emby/embyserver:latest
    container_name: embyserver
      #runtime: nvidia # Expose NVIDIA GPUs
    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=0 # The UID to run emby as (default: 2)
      - GID=0 # The GID to run emby as (default 2)
        #- GIDLIST=100 # A comma-separated list of additional GIDs to run emby as (default: 2)
    volumes:
      - /mnt/nas/embyconfig:/config/ # Configuration directory
      - /mnt/nas/TV_shows:/tvshows # Media directory
      - /mnt/nas/Movies:/movies # Media directory
      - /mnt/nas/Music:/music
      - /mnt/nas/Photos:/photos
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
        #devices:
        #- /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes
        #- /dev/vchiq:/dev/vchiq # MMAL/OMX on Raspberry Pi
    restart: unless-stopped

[mastrmind11 722]

try removing the / after config

[rtangwai 1]

I sorted it out - turned out to be a Docker issue, the original install was a Snap package which did not work well.

Reinstalling Ubuntu 22.04 w/o Docker during the base OS and installing Docker directly from the repository fixed it.

[Luke 42078]

Thanks for following up.