seafile.sh fails if the seafile-data does not belong to the user running the script in Docker

[deragon]

Error: the user running the script ("root") is not the owner of "/shared/seafile/seafile-data" folder, you should use the user "UNKNOWN" to run the script.

This is the error when starting the Docker following instructions found at Migrate from non-docker Seafile deployment to docker. I am using Method 1. On the host, user seafile (500) is owner of anything under /opt/seafile, including /opt/seafile-data/seafile/seafile-data.

No where in the documentation is this user mis-matched mentioned and a solution provided.

Ideally, the script should detect it is running under docker and should adapt accordingly.

[deragon]

Not tested, but one solution is to have a user and group named 'seafile' in the Docker image of Seafile, with say uid and gid 9876 which is unlikely to be used on a regular host. Then, one can ask to create this same user and group on the host and chown the host files to that user. The script should then run under the 'seafile' user within the Docker.

[deragon]

Come to think of it, the uid/gid could be passed as a parameter in the docker-compose.yml file.