I was missing an important part of setting up a local joplin-server.
Probably it is a nice add on in the doc.
For running on an Ubuntu 24.04.4 LTS (Noble Numbat) I missed the follwing settings to get the server up and running as a docker container.
I do not know if it applies inly to ubuntu but I could imagen rather not.
I did not see it in the joplin-server's README.md, but it was necessary.
Before the change all file rights were given to my user which is the administrative user of the os.
# Change ownership of the data folder to the ID Joplin uses
sudo chown -R 1001:1001 ~/joplin-server/data
# Ensure the folder has write permissions
sudo chmod -R 755 ~/joplin-server/data
I've never needed to change ownership or permissions and I have set up Joplin server over the years on both Ubuntu and Debian systems.
Joplin Server's data from the container that is in the mapped folder appears as user 999 on my system, certainly not 1001, that could easily be another user's account on the host system. Being 999 occurs without any intervention needed from me and effectively locks me out of the data folders unless I sudo su. I believe that in the past it was been asked if it would be possible to set the UID and GID in the compose file.
Also I cannot see why the data folders would need "execute" for OWNER and GROUP and PUBLIC for Joplin Server to work??
Are you happy with your Docker config?