Thanks. That took me quite a bit of time to figure that one out. Probably, it is better to use the --json interface. That is a bit more comprehensive.
I am running into another issue. When I want to run rclone in docker as another user (non admin) as explained in: https://rclone.org/install/#install-with-docker, there is a problem with the cache directory as the /etc/passwd is inherited from the host (home does not exist) I thought of changing the cache directory with --cache-dir, but with the "rclone rc" command, it seems not to have any effect (unless I am doing something wrong )
I start the container as follows. The --cache-dir option works here (without it I get an error)
I was confusing the permissions on the docker container with the wanted permissions on the target file system. Still, if you are running the docker container with the "--user $PUID:$PGID" option on any other user besides the root user, you get very strange behavior:
not all the remotes in your rclone.conf are visible (only the first one?)
you cannot mount the container with "rclone rc mount/mount"
Anyway, after digging deeper in the forum posts, I came to the following solution to do the following
Mount cloud storage for a specific user / group.
Modified the default permissions (user: all, group: read, world: none) (umask 027 --> integer 23)
Mount multiple cloud storages.
Everything via an installation of rclone via docker (which is preferable for me, since it is running on a NAS).
Thanks for tip. --cache-dir was not working here because I executed the docker container with a '--user' parameter that was not root. Lots of weird things happened, so I just leave it to run under root.
Can you actually set it through rclone rc options/set? I could not find a parameter.
I also was wondering about the units of time for e.g. CacheMaxAge. It looks like to be nanoseconds? (default is 1h = 3600s, and it is listed as 3600 with 9 additional zeroes).