After restarting the Docker container, my rclone.conf file is gone

The /root/ directory within the container is volatile. When you stop the container (or restart the machine on which the container is running), the container is “thrown away” and recreated from the image upon restart. Anything not located within a volume (like /config) is then permanently lost.

BmuS prevents this by checking if an rclone.conf file exists in the Docker container. If so, BmuS checks if an rclone.conf file is located in the /config folder on the host. If it is not, or if the file is empty (0 Bytes), BmuS copies the rclone.conf file from the Docker container to the /config folder.

However, this only happens if CLOUD_BACKUP=1 is set in the bmus.conf file. If this is not the case, and you restart the container without this process having been carried out at least once AND directly after you have configured rclone, the rclone.conf file in the Docker container will be lost the moment you restart Docker.

Unless you plan to use cloud backup but still want to configure rclone in the Docker container prior performing a cloud backup, it’s best to manually copy the rclone.conf file from the container to the /config directory.

Reconfigure rclone (if necessary):

docker exec -it bmus_backup rclone config

Manually copy the rclone.conf file into the /config folder:

docker exec -it bmus_backup cp /root/.config/rclone/rclone.conf /config/rclone.conf