Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get Rclone working #35

Closed
quarthio opened this issue Oct 2, 2022 · 4 comments
Closed

Can't get Rclone working #35

quarthio opened this issue Oct 2, 2022 · 4 comments

Comments

@quarthio
Copy link

quarthio commented Oct 2, 2022

From the instructions in https://github.com/dadatuputi/bitwarden_gcloud/blob/master/.env.template I try to setup Rclone backups. When running the following command:

sudo docker exec -it bitwarden rclone config --config $BACKUP_RCLONE_CONF

I get the following error:

OCI runtime exec failed: exec failed: unable to start container process: exec: "rclone": executable file not found in $PATH: unknown

Which I couldn't fix. Please help me out.

@ilyadel
Copy link

ilyadel commented Nov 15, 2022

Rclone is not yet installed on bitwarden container. you can do it by launching the command :
sudo docker exec -it bitwarden ash /backup.sh rclone
The backup will probably fail, but the script will install rclone and you can continue the configuration.

@frankyboy1604
Copy link
Contributor

frankyboy1604 commented Nov 16, 2022

This worked for me. My steps:

  1. configure .env File for rclone backup.
  2. restart container
  3. Run the following command: sudo docker exec -it bitwarden ash /backup.sh rclone
  4. Run the following command to configure rclone sudo docker exec -it bitwarden ash -c 'rclone config --config $BACKUP_RCLONE_CONF'
  5. Configure rclone with remote setup
  6. Enter as name for the new remote only remote

@dadatuputi
Copy link
Owner

dadatuputi commented Nov 18, 2022

Hey @frankyboy1604, I see your pull request #37. Nice work. Asking here because you laid it out, but why your 6th step? I have a working rclone config that has a name other than remote. Why is that necessary?

@frankyboy1604
Copy link
Contributor

You are right. The problem was that I used a name like 'dropbox remote' with spaces in it. I fixed it in the backup.sh script. Now you can use remote names with spaces in it.
The 6th step ist not necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants