taverty

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by taverty

  1. It has been a while. But from what I remember I just exec'd into the container and ran the ./account_setting.pl script. Pretty sure it asked for my password during that script run. To Exec into the container run the following command at the unRAID command prompt: docker exec -it idrive /bin/bash The above command will bring you to a bash prompt inside the idrive docker container. Once at that prompt, run the following command: ./account_setting.pl The directory in the idrive container should be: /opt/idrive/IDriveForLinux/scripts Once you're in the container you can run all the iDrive scripts as if you were running them on a standard Linux installation.
  2. There is no GUI on the local unRAID server. Once connected to iDrive you can use the iDrive GUI to setup the backup. Your unRAID server will show up as an available client.
  3. As a side note, if you want the nice iDrive icon to show in your Docker view list use the following link for the Icon URL: https://static.idriveonlinebackup.com/source/images/favicon.ico The option is under the Advanced View.
  4. You'll need to setup your persistent mappings in unRAID like the docker-compose example. I attached a screenshot showing my setup. Be sure to create an empty idrivecrontab.json file on you local system before starting the container. Use the touch command, (touch /mnt/user/appdata/idrive/etc/idrivecrontab.json) in a terminal. All mappings are Read/Write with the exception of the backup_dir, that's set to Read Only.
  5. I wrote a fully functioning iDrive docker container about a year ago. It has been working flawlessly since. Auto restarts on server reboots and retains the configuration. Just make sure to read the installation section and create an empty idrivecrontab.json file before starting the container. Only needs to be done once. Also follow the "First Run" section as well. https://hub.docker.com/r/taverty/idrive