My Turn...A proper working Insync image for the Raspberry Pi
Insync requires you download their bz2 "portable" package for utilization on rpi. Luckily,
insync-portable operates almost exactly the same as
insync-headless does meaning most commands work exactly as intended.
My changes include:
- Dockerfile now downloads armhf release
- Launcher is now in line with running portable out of its extrated directory
- s6 executes a pre and post script by utilizing
99-insync-setupwhich runs after the service as started to configure your account!
- Removed a bunch of guck like zabbix config, licensing, etc..
Things I should still do:
- Add more logging about what the script is doing for verbosity
- Cleanup any statically defined references that could utilize a variable instead (i.e.
- Actually test multiple accounts works?
- Insert option to not automatically start syncing (a
- Modify and test helper scripts for managing your account manually.
Note I modified this container for my use hence it is missing a few checks and niceties (including testing). I don't recommend you try using this unless you know what you're doing and like rolling up your sleeves. However, it will work swimmingly given you pass the right variables and have no alternate plans...
Dockerfile to build an Insync container image to synchronize Google Drive.
Supports Multiple Accounts
This Container uses a customized Debian Linux base which includes s6 overlay enabled for PID 1 Init capabilities, zabbix-agent based on TRUNK compiled for individual container monitoring, Cron also installed along with other tools (bash,curl, less, logrotate, nano, vim) for easier management. It also supports sending to external SMTP servers..
Table of Contents
- Quick Start
You must have a license for Insync and authorize your Google Account with the Application.
Automated builds of the image are available on Registry and is the recommended method of installation.
docker pull tiredofit/insync:(imagetag)
The following image tags are available:
latest- Most recent release of Insync w/Debian Jessie
Visit https://goo.gl/jv797S to authorize Insync for your Google Drive Account
Set various environment variables to understand the capabilities of this image.
Map persistent storage for access to configuration and data files for backup.
The container will create a folder for the account to be synced upon startup.
The following directories are used for configuration and can be mapped for persistent storage.
||For configuration storage and Databases|
||Root Backup Directory|
Along with the Environment Variables from the Base image, below is the complete list of available options that can be used to customize your installation.
||Primary Your GDrive Username e.g.
||Primary Authorization Code provided by Google|
||Primary How to download files
||Secondary Your GDrive Username e.g.
||Secondary Authorization Code provided by Google|
||Secondary How to download files
||Third Your GDrive Username e.g.
||Third Authorization Code provided by Google|
||Third How to download files
||Type of Proxy
||Name of Proxy Host e.g.
||Port of Proxy e.g.
||(Optional) Username for Proxy e.g.
||(Optional) Password for Proxy e.g.
No Ports Exposed
Selectively Syncing Files
- Enter the container and execute
manage_syncand use the Ncurses Interface
- Enter the container and execute
manage_ignoreand use the Ncurses Interface
For debugging and maintenance purposes you may want access the containers shell.
docker exec -it (whatever your container name is e.g. insync) bash