I still had issues when manually creating the directory. My service container was unable to see any data from the Google Drive mount.
Maybe it is related to the missing shared flag.
Going the route described in 1.57 seems to cause "Directory already mounted, use --allow-non-empty to mount anyway" error under docker - #5 by ncw via the mount placed in some user directory works if you start the containers in the correct order: first the rclone, then the service. A reboot which starts both at the same time break this setup.
I switched to the docker plugin which seems to be the most robust solution: