Silverbullet docker creates files as root since 2.10

Troubleshooting
1

Good day everyone!

I have noticed that since 2.10 my SilverBullet ran in docker started to create files as root. Before that it used the owning user of the /space folder to do that. So I could easily do some changes from OS.

I have tried setting PUID=1000 and PGID=1000 explicitly in docker-compose.yml but it doesn't seem to change anything.

I have recreated the whole setup with multi-space. And still everything is creates as root.

First of all have you noticed the same behaviour? Did you find a fix? Or is it the expected new behaviour?

2

Yes, this was a regression that I fixed on the edge builds already. I hope to do a 2.11 release tomorrow.

3

Good! Because renaming doesn't work in cases where pages belong to different users. And probably some other things too.

Thanks for a quick answer.

4

Just in case this helps somebody with the update, I have to modify the file permissions on the files or the 2.11 docker container wouldn't start, ex:

sudo docker logs --tail 200 aebdcd513a02
Warning: mounting your space at /space is deprecated, mount the data folder at /data instead
Will run SilverBullet with UID 3000, inferred from the owner of /space (set PUID environment variable to override)
Creating 'silverbullet' group (with GID 0) and 'silverbullet' user (with UID 3000) inside container
Running SilverBullet as user configured with PUID 3000 and PGID 0
Error: could not read /space/users.json: Permission denied (os error 13)
2026-09-17T16:10:56.432513Z  INFO silverbullet::server: SilverBullet 2.11.0-0-g3b669b81-2026-09-17T13-06-11Z
2026-09-17T16:10:56.432567Z  INFO silverbullet::server: Data folder: /space
2026-09-17T16:10:56.432627Z ERROR silverbullet: could not read /space/users.json: Permission denied (os error 13)

I also had my data mounted as /space, modified it to /data while I was there.

5

What did you have to do exactly? This is not clear to me.

6

I had to sudo chown -R 3000:0 /... my data directory to make it work.