Open jcotton42 opened 2 years ago
Rclone seems to want to maintain updated refresh tokens in the config file, which is not practical when you want to attach a pre-existing one from a secret. I would have to research more if/how that can be avoided. Feel free to post anything else you find here.
The first solution that comes to mind is mounting the secret in the container somewhere else, then copying it to where mc-backup expects to see it on first start. I'll try an entry point workaround like I did for the RCON password later today.
I'm getting multiple "failed to save config" errors in the logs for mc-backup. I suspect they're actually coming from rclone, but I'm unsure so I'm asking here first.
This is how mc-backup is configured
It looks like rclone (?) is trying to move rclone.conf, but that's not working since it's mounted into the container by Docker. Any ideas on what to do? It's a not deal-breaker since the backups still work, but it would be nice to have less noise in my logs.