#The /app/config volume mount was not configured properly.

8 messages · Page 1 of 1 (latest)

storm rain
#

I am spinning up Overseer on my Synology using Container Manager. When I open up the configuration page, I receive the following error, and obviously I lose my configuration when I restart the project.

The /app/config volume mount was not configured properly. All data will be cleared when the container is stopped or restarted.

---
services:
  overseerr:
    container_name: overseerr
    environment:
      - PUID=1027
      - PGID=100
      - TZ=America/Denver
    image: sctx/overseerr:develop
    ports:
      - '5055:5055'
    restart: unless-stopped
    volumes:
      - /volume1/docker/appdata/overseerr/config:/config

My compose is using the same settings as all my other projects for PUID/PGID, and the volume path is valid.

image.png
#

The logs don't give me any obvious clues.

Apologies for screen shot, Discord character limits are too small. 😥

scenic roost
storm rain
#

I don't care for the way he builds his projects, but there are a couple of good help articles on there about correctly setting PUID/PGID, as well as folder ownership and permissions.

scenic roost
#

Thanks for sharing your thoughts! I understand that different approaches work for different people. I'm glad you found the articles on PUID/PGID and folder ownership/permissions helpful—that's what matters in the end.

sonic star
storm rain
#

I messed with permissions and users for a bit yesterday without luck. Today I changed from the sctx image to the lscr.io image and everything worked first try.

#

Latest is pretty old though. 😦

image.png