Fix recordings bind mount permissions for non-root container user #25

Merged

wandabastyle merged 2 commits from docker into main

2026-04-29 20:38:56 +02:00

wandabastyle commented

2026-04-29 20:36:51 +02:00

(Migrated from github.com)

Summary

This PR makes the recordings bind mount more explicit and documents how to prepare the host-side folder when the container runs as UID/GID 1000:1000.

The app container is configured to run as a non-root user:

user: "1000:1000"

Because ./recordings is a bind mount, Docker uses the host folder’s real filesystem ownership and permissions. If the host folder is not writable by UID/GID 1000:1000, the app can fail when trying to create or write recordings under /app/recordings.

## Summary This PR makes the `recordings` bind mount more explicit and documents how to prepare the host-side folder when the container runs as UID/GID `1000:1000`. The app container is configured to run as a non-root user: ```yaml user: "1000:1000" ``` Because `./recordings` is a bind mount, Docker uses the host folder’s real filesystem ownership and permissions. If the host folder is not writable by UID/GID `1000:1000`, the app can fail when trying to create or write recordings under `/app/recordings`.