I am tryign to dockernize filestorm so that it can be run from NAS device.
Current latest version 2.0 https://github.com/MOACChain/FileStorm/releases/tag/2.0
scsserver-linux-amd64 cannot be started in docker container with non-root privilege.
After further investigation, it turns out scsserver-linux-amd64 was trying to write files in the root directory.
- /private.pem
- /public.pem
- /scskeystore/
Those files are out of /data/scs directory which is configured in userconfig.json
{
//....
"DataDir" : "/data/scs"
//...
}
However, scsserver-linux-amd64 does not respect that. And encountered permission error on start.
A temporary solution is to add the following line into Dockerfile so that the working directory is fixed to /data/scs.
It seems scsserver-linux-amd64 is trying to write files in working directory instead of configured path.
I am tryign to dockernize filestorm so that it can be run from NAS device.
Current latest version 2.0 https://github.com/MOACChain/FileStorm/releases/tag/2.0
scsserver-linux-amd64cannot be started in docker container with non-root privilege.After further investigation, it turns out
scsserver-linux-amd64was trying to write files in the root directory.Those files are out of
/data/scsdirectory which is configured inuserconfig.jsonHowever,
scsserver-linux-amd64does not respect that. And encountered permission error on start.A temporary solution is to add the following line into Dockerfile so that the working directory is fixed to
/data/scs.It seems
scsserver-linux-amd64is trying to write files in working directory instead of configured path.