immich-kiosk - configuration file - cannot get use of it

[Kon-Stan-Can]

Hi,

I have immich-kiosk on QNAP NAS in docker. It works fine.

The only I cannot get use of config file. I'd like to use weather, but it's configuration is available only in config file config.yaml.

I have the following setting in docker-compose.yml:

immich-kiosk:
container_name: immich-kiosk
image: ghcr.io/damongolding/immich-kiosk:latest
...
volumes:
- /share/Container/immich/immich-kiosk-Config:/config

Directory is like this:
immich
immich-kiosk-Config
config.yaml

Directory immich-kiosk-Config was created by immich-kiosk.

When I run:
docker logs immich-kiosk

I get:
12:08:41 ERRO Failed to initialize config state err="getting initial file mTime: stat : no such file or directory"

I have settings in config.yaml file to display clock like:
show_time: true
time_format: 12 # 12 or 24

But no clock.
If I turn on clock through env variables or command line, clock shows.

Thanks for help!

[darekwojciechowski]

The useful part of that error is the empty filename: stat : no such file or directory. Kiosk is calling stat on nothing, which means it never loaded a config file at all, so the watcher has no path to follow. Your config.yaml isn't reaching the container.

Inside the container it only looks in / and /config/, and it runs as nonroot, not root. So:

docker exec immich-kiosk ls -la /config

My guess is the file won't be there. On QNAP, if the container was first created in Container Station's UI, the UI keeps its own volume list and editing docker-compose.yml afterwards doesn't change what's mounted. Recreating it rather than restarting picks up the compose file:

docker compose up -d --force-recreate immich-kiosk

If config.yaml does show up in that listing, then it's a read permission problem for the nonroot user instead, and chmod 644 on the file fixes it.

[Kon-Stan-Can]

Thanks for reply.

docker exec immich-kiosk ls -la /config

gives me:
OCI runtime exec failed: exec failed: unable to start container process: exec: "ls": executable file not found in $PATH: unknown

just running:
ls -la /share/Container/immich/immich-kiosk-Config

gives me:
drwxr-xr-x 3 admin administrators 4096 2026-07-27 18:19 ./
drwxrwx--- 15 admin MINYA\domain users 4096 2026-07-27 18:30 ../
drwxrwx--- 2 admin administrators 4096 2026-07-27 18:19 config/
-rw-r--r-- 1 admin MINYA\domain users 5858 2026-07-26 11:09 config.yaml

I tried to set:
chmod 644 on file.

Container immich-kiosk was created from command line. Nevertheless, I tried:
docker compose up -d --force-recreate immich-kiosk

Nothing helps.

Running docker logs immich-kiosk
still shows:
18:21:34 ERRO Failed to initialize config state err="getting initial file mTime: stat : no such file or directory"

Anyway, thanks for help!

[damongolding]

What happens if you change your compose mount to this?:

volumes:
  - /share/Container/immich/immich-kiosk-Config/config.yaml:/config.yaml

[Kon-Stan-Can]

Additional information.
I tried the following:

Changed configuration to:
volumes:
- ./config:/config

and got an error:

err=
│ config directory permission is 777, it should be 755
│ config file "config" not found in "[/ /config]"

Once I corrected chmod to 775 to directory 'config', I got back to log:
11:53:32 ERRO Failed to initialize config state err="getting initial file mTime: stat : no such file or directory"

File config.yaml is present in 'config' directory.

[damongolding]

Pretty much what @darekwojciechowski said. I would add that you should probably make the directory and config file yourself, rather than letting docker create them for you.

[Kon-Stan-Can]

Thanks. I tried both ways - to create by myself, to rely on folder creation by immich-kiosk.
At least when it is created by immich-kiosk, I would assume, that fodler ipath is correct.

Thanks anyway.

[thomasgeens]

Hi @darekwojciechowski

Ran into the same issue (as usual with Docker on my QNAP 😆) The problem isn't the config file path or permissions mode, it is a UID mismatch.

Root Cause:

• Your config file was owned by your user (e.g., admin or your QNAP username)
• But the immich-kiosk container runs as nonroot with UID 65532 inside the container
• QNAP's Docker uses user namespace remapping for security, so when the container tried to read the file, it couldn't because UID 65532 didn't own the file on the host
• Result: "permission denied" even though the file mode was technically readable (644)

Note: Normally with docker-compose you can disable the user namespace remapping at service level with userns_mode: host, but for some reason Container Station's own Docker implementation doesn't pick up or overwrites this setting.

The Fix:

Change the file ownership to UID 65532:

chown 65532:65532 /share/Container/immich/immich-kiosk-Config/config.yaml
chmod 644 /share/Container/immich/immich-kiosk-Config/config.yaml

Then restart the container via Container Station, Portainer, whatever you use or shell:

docker-compose down
docker-compose up -d --force-recreate immich-kiosk

Why this works:

Now when the container's nonroot user (UID 65532) tries to read the file, it's actually the file owner, so permission is granted.

Note: The --force-recreate flag is important on QNAP because Container Station may cache volume mounts even after docker-compose changes.

Hint: Maybe just mount only the config.yaml file and not the whole config directory e.g., - "/share/Container/immich/immich-kiosk-Config/config.yaml:/config/config.yaml:rw"

Hope this helps!

[Kon-Stan-Can]

It works.

I additionally changed config line to:
- ./immich-kiosk-Config/config.yaml:/config

Regards,
Konstantin.