Grive2

Grive2 is an archived Docker image that used the grive2 command-line client to sync Google Drive files to a local path on a cron schedule for homelab users,…

  • Backup
  • Cloud
  • Network Services
  • Productivity
  • Tools & Utilities
Grive2 is an archived Docker image that used the grive2 command-line client to sync Google Drive files to a local path on a cron schedule for homelab users, but it no longer works because Google changed the Drive API integration.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

28/100 Low

Maintained
0GitHub repository is archived
Popular
209 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
85no serious findings, CI

Availability: platform listings confirmed today, links checked 41 days ago

GitHub stars
9
Open issues
3
Last commit
2023-02-03
Latest release
1.3.2
License
GPL-3.0
Activity
stale

Checked 18 days ago - source: GitHub (agusalex/grive2docker)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Deprecated The developer confirms Google broke the Drive API integration and this image no longer works. The repository is archived. Do not deploy for new use cases. source
  • Deprecation This Docker image no longer works because Google broke the Drive API integration; do not deploy it for backups. source
  • No longer functional Do not install or update; Google broke the Drive API integration, so the container no longer syncs files. source
  • Warning This Docker image no longer works because Google broke the Drive API integration. source
  • Archived repository The repository is archived and the Docker image no longer functions; do not deploy it for new Google Drive sync. source
  • Deprecation warning Do not deploy this image for new use: the repository is archived and the Docker image no longer works because Google changed the Drive API integration. source

Fetched 3 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I sync only specific Google Drive folders?

Yes. Set the PARAMS environment variable to pass grive2 flags such as -s folder_name; otherwise it syncs all Drive folders and files to the mounted path.

What Google authorization information does the container need?

It needs a client ID and client secret from a Google OAuth client credential created as a TV device type, plus an authorization code from the initial grant-access flow.

How do I set the sync schedule?

Set the CRON environment variable to a crontab expression; the container runs the grive2 sync on that schedule.

Can I set Unix file permissions on the synced files?

Yes. Use the PERM environment variable to specify Unix permissions applied to all files in the folder.

How is the Docker image updated?

The snapshot tag is rebuilt automatically on Docker Hub on the first day of each month from the master branch of grive2.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads