docker compose volumes not mounting files

Hello! I have a HomeAssistant app running using the following docker compose:

services:
  homeassistant-1:
    image: ghcr.io/home-assistant/home-assistant:2025.3.3
    container_name: homeassistant-1
    restart: unless-stopped
    networks:
      - tipi_main_network
    environment:
      TZ: ${TZ}
    ports:
      - ${APP_PORT}:8123
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${APP_DATA_DIR}/data/config:/config
...

services:
  homeassistant-1:
    image: ghcr.io/home-assistant/home-assistant:2025.3.3
    container_name: homeassistant-1
    restart: unless-stopped
    networks:
      - tipi_main_network
    environment:
      TZ: ${TZ}
    ports:
      - ${APP_PORT}:8123
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${APP_DATA_DIR}/data/config:/config
...

The problem is that the /config volume is not mounted. It was mounted when I started for the first time, but then it stays the same even if I change the files outside of the container.

5 Replies

InfBoumcyCastle•2mo ago

Every intended change to the standard compose has to be done in a user config. The compose in apps/ gets recreated at start to its original state. https://runtipi.io/docs/guides/customize-app-config

Customize app config

Homeserver management made easy

KhaosDoctorOP•2mo ago

Thanks! But I think I misspoke a bit. The composer file is fine. The problem is the actual file. The HomeAssistant container creates a volume inside the composer container, this volume should be updated with the files outside of the container when the container starts up, however, the files are not being updated, if I change the file outside (in my own file system) it doesn't update inside, not even if I issue a rebuild or force recreate manually, the only solution I could find is to manually copy using docker cp, but I still haven't test file watch mode

InfBoumcyCastle•2mo ago

maybe a permission problem? i use homeassistant-1 but did not edit any files for the container. it seems though that the files has to be owned by root:root . are the affected files owned by root?

KhaosDoctorOP•2mo ago

Yes, I think all the files in tipi are running as root

InfBoumcyCastle•2mo ago

what change are you trying to make? i can try and recreate it on my end

Gaming

Programming

docker compose volumes not mounting files

Did you find this page helpful?