controlol/gdrive-rclone repository overview

⁠gdrive-rclone-docker

⁠Introduction

This Docker image is used to mount to your Google Drive folder to a local folder. All files will appear as if they are locally on your system and you can browse like you normally would. Added files will at first be stored locally and pushed to Google Drive once per 6 hours. This will allow quick access to newly created files. Secondly there is a configurable cache pool to further improve the experience.

If you want to use the Google Drive space on your local network you can share the mounted folder as a SMB or NFS share.

⁠Usage

This image will require some special flags to function properly, this is because you will be mounting mergefs (fuse) to a shared docker volume. Add the following flags to you docker cli --cap-add SYS_ADMIN --device /dev/fuse.

To Use Rclone with Google Drive you will need to allow access to your Google Drive API.

⁠Prerequisites

You will need to have rclone installed on your machine or in a temporary docker container. Obtain a Google Drive API client id and secret following this guide from Rclone⁠. Somewhere in your drive you will need to create a root folder for you Rclone files to live. I would suggest calling it rclone. The RCLONE_FOLDER will live inside this folder. Open the folder in Google Drive and copy the folder id.

⁠Create base rclone configuration

Once you have the client id, client secret and folder id you can run the command rclone config, this will prompt you with a couple of questions.

n - Creates a new remote
gdrive - Give your new remote a name, same as RCLONE_REMOTE
drive - Selects Google Drive
client_id - Enter the client ID you obtained previously
client_secret - Enter the client secret you obtained previously
1 - Enables access to the entire drive
root_folder_id - Enter your folder id from the created folder before
service_account_file - Leave blank and continue
y - Edit adavnce config

After this you want to keep clicking enter and use default options until you reach:

Remote config
Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine
y) Yes (default)
n) No

Unless you are running the command on a PC with a browser you will want to choose no. It will give you a link you can paste in your browser. Take the steps and allow access to the folder. Once finished you will get a code and paste this in de Rsync terminal. Continue with the last two options.

n - Do not configure as team drive.
y - Accept the config.

Using the command rclone config file, you will get the location of the created config file. Copy this file to the folder where you plan to mount the config folder of the container and name the file gdrive-rclone.conf. This config will be used as a base configuration. The encrypted remote will be added automatically once you start the container.

⁠Docker CLI

docker run -d \
  --name=gdrive-rclone \
  --net=bridge \
  -e TZ=Europe/Amsterdam \
  -e PASSWORD=yourpassword \
  -e PASSWORD2=yourpassword \
  -e RCLONE_FOLDERS=remote1,crypt,move;remote2,nocrypt,copy \
  -e RCLONE_REMOTE=yourremote \
  -e CACHE_MAX_SIZE=250G \
  -e CACHE_MAX_AGE=12h \
  -v /path/to/config:/config \
  -v /path/to/localstorage:/local \
  -v /path/to/merged:/merged:rw,shared \
  --cap-add SYS_ADMIN --device /dev/fuse \
  --restart unless-stopped \
  controlol/gdrive-rclone

⁠Volumes

Make sure you have created the rclone base configuration⁠ and copied it to /config/gdrive-rclone.conf.
The /local directory contains two folders, gdrive and cache. The gdrive folder is temporary storage for files that were copied to /merged but still have to be uploaded to Google Drive. The cache folder has temporarily downloaded files from gdrive, and will not grow beyond CACHE_MAX_SIZE. Each remote will have it's own subdirectory inside the cache and gdrive folder.

⁠File uploads

Every six hours files will be moved to Google Drive, a file is only considered if it is older than 6 hours

⁠Environment

The RCLONE_FOLDERS environment can be used to create one or more remotes. Each remote is seperated by a semicolon, settings for the remote are separated with a comma. There are two settings. You can skip one or both options, the default value will be used. The first setting is used to enable encryption of the uploaded folder, if you want to encrypt the uploaded folder enter crypt as the value. The second setting determines the command you want to use to upload, the default value is move. However you can choose copy if you want to keep all the files locally as well.

⁠Rclone remote examples

⁠Mounting a merged volume to another container

It is possible to use the merged folder in other containers. The easiest way would be to directly mount one (or more) of the subfolders directly to the container. However this will not work when the gdrive-rclone container is restarted. Therefor it is recommended to mount the merged parent folder directly in slave mode. This will give the container access to all of your mounts.

⁠Example

First option:

docker run -d \
  -e FOLDERS=remote1,nocrypt,move \
  -v /path/to/merged:/merged \
  --cap-add SYS_ADMIN --device /dev/fuse \
  controlol/gdrive-rclone:latest
  
docker run -d \
  -v /path/to/merged/merged1:/container/path/merged1
  ubuntu:latest

The Ubuntu container needs to be restarted after the gdrive-rclone container has restarted.

Second option:

docker run -d \
  -e FOLDERS=merged1,nocrypt,move \
  -v /path/to/merged:/merged \
  --cap-add SYS_ADMIN --device /dev/fuse \
  controlol/gdrive-rclone:latest
  
docker run -d \
  -v /path/to/merged:/container/path:slave
  ubuntu:latest

The Ubuntu container does not have to be restarted after gdrive-rclone has restarted. After the gdrive-rclone container's state is up the subdirectories will work again.

By no means are these examples complete with all the necessary volumes and environments but it shows a basic example how the folder structure works.

⁠Notes

It is recommended to use a random string for PASSWORD and PASSWORD2 between 64 and 128 characters, they should not be the same string.
Your CACHE_MAX_SIZE should be at least as the size as the largest file you expect to upload.
Setting USE_COPY will allow you to keep the files locally, they will still be uploaded on the same schedule.
A move job will not run for longer than 6h to prevent multiple jobs running at once.
The maximum upload limit is 750GB per day.