For the long term solution, I asked the author of the backup program to make DATA_DIR an environment variable, which they did starting in version 1.6.0. This is only good until a restart of the container. Using Portainer.io, an Exec Console was opened in the (bitwardenrs_backup) container and the /app/includes.sh file was edited to change DATA_DIR="/bitwarden/data" to DATA_DIR="/data". This (I hope) only required a change to the includes.sh file in the bitwardenrs_backup container. HISTORY LESSON HERE: What was not noted in the reference was that the scripts pointed to /bitwarden/data as the Bitwarden data directory, which differs from the above installation instructions. The other environment variables maintained their default values.Į. Setting up the Bitwarden Server Step 1: Setting up your Linux server Step 2: Provisioning your Bitwarden Server Step 3: Running your Bitwarden Server locally Step 4: Exposing your new server publicly Step 5: Connecting to your new Bitwarden instance from a client. The environment variables RCLONE_REMOTE_NAME, ZIP_PASSWORD, and TIMEZONE were set accordingly. As noted in the reference, the command for starting the (vaultwarden_backup) backup container required changing "-volumes-from=vaultwarden" to "-volumes-from=Bitwarden" for the above installation instructions. sudo docker run -rm -it -mount type=volume,source=vaultwarden-rclone-data,target=/config/ ttionya/vaultwarden-backup:latest rclone config showĭ. sudo docker run -rm -it -mount type=volume,source=vaultwarden-rclone-data,target=/config/ ttionya/vaultwarden-backup:latest rclone configĬ. sudo docker pull ttionya/vaultwarden-backupī. sudo dpkg -i libseccomp2_2.5.1-1_bįollowed the instructions for using Google Drive as the backup targetĪ. In anticipation of a problem with cron when using docker on a Raspberry Pi 3B+ (See the relevant closed issue on the Reference website), installed the most recent version of libseccomp2ī. This has the effect of creating one file per day in the directory, but having 24 downloadable versions of it for at least 30 days. The format of the backup file name is backup.%Y%m%d. The reference program allows me to implement automatic backups of the vaultwarden database to a directory on Google Drive every hour. Followed the rest of the instructions in the reference. After that, the state of the nginx_app_1 container changed to healthy.ģ. The solution was to delete the existing auth table (and similarly, the user table).Ĭ. After that, the log showed repeated entries of not being able to create the table "auth" because it already existed. Instead, the log file had repeated entries of "can't take lock to run migrations migration table is already locked." The solution was to go into nginx_db_1 and delete all the rows from the migrations_tableġ) docker exec -ti nginx_db_1 mysql -h 172.18.0.2 -P 3306 -u npm -p npmī. Step 11 says to wait for the status of nginx_app_1 to change to healthy, but it didn't. Installed nginx proxy manager according to these instructions: Ī. Installed Docker and Portainer according to these instructions: Ģ. Reference: (Pay attention to the updates caused by the name change to vaultwarden)ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |