Open SkypLabs opened 1 year ago
can confirm same behaviour on my arch machine, looking into this and your solution!
Any new developments with this issue? Running into the same "Permission Denied" error
I think the problem comes from the assumption that one would run the generate
command of the start.py
tool as described here prior to starting the service. The generate
command changes the ownership of the data directory whereas Synapse itself does nothing about it when spinning up a new instance.
Description
By default, the official Docker image runs with both UID and GID set to
991
. This creates permission issues when using Docker volumes (not bind mounts).Steps to reproduce
Here is a sample Docker Compose configuration file to reproduce the issue:
The following Synapse configuration files must be placed in
envs/dev/config/synapse/
:homeserver.yml
:log.config
:signing.key
Homeserver
Local deployment with Docker
Synapse Version
v1.75.0
Installation Method
Docker (matrixdotorg/synapse)
Database
SQLite
Workers
Single process
Platform
Docker engine running on Debian 11.
Configuration
No response
Relevant log output
Anything else that would be useful to know?
This issue seems related to https://github.com/matrix-org/synapse/pull/6389 which fixed a similar problem when generating a Synapse configuration file with the official Docker image.