abra app backup operates on compose files that are not in use
#632
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#632
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
abra app backupruns the commands listed under deploy->labels->backupbot* for each compose*.yml file in the directory for a given recipe.This causes an error when an optional compose file is included in a recipe but is not being used (i.e. it's not referenced in the config).
For example in the nextcloud recipe, compose.mariadb.yml and compose.postgres.yml are both included, and both include backup commands.
Typically only of these databases is enabled, via the configuration. But
abra app backuptries to run the backup commands for both mariadb and postgres, and errors out on the one that hasn't been installed.Hey @marlon 👋 Thanks for raising this. That does seem to be a pretty bad bug. The thing is at the moment is that we're 50%+ through a re-design/implementation of the backup system that uses https://git.coopcloud.tech/coop-cloud/backup-bot-two It would be quite tricky to patch and release the fix atm 🤔
Can you provide which abra version and which backup-bot-two version you are using?
The new backupbot version (main branch) fetches the commands only from the running container. If a container is not running it's not able to get the pre/post commands:
client.services.list()is equivalent todocker service lsand lists only running services. Can you rundocker service lsand look which services are running? Is there maybe an old zombie container left?Thanks for your attention! I was using abra version 0.9.0-beta-e3a0af5 and not using backup-bot-two, just the
abra backupcommand documented here: https://docs.coopcloud.tech/operators/handbook/#how-do-i-backuprestore-my-appBut thanks to @decentral1se 's note I now understand that
abra backupis not currently supported, and the fix is to use backup-bot-two instead. If appropriate I could update the above linked docs to reflect this?@marlon thx, yeh maybe pointing to anything with issue label "backups" + "bug" and saying we're working on the new version and trying to avoid dealing with backporting fixes atm... something something "try out
backup-bot-two? Unsure... it's all a bit unstable atm. i know a couple of collectives are usingbackup-bot-twoa lot so you could get some additional help from the Matrix tech channel 🙏Related coop-cloud/nextcloud#43 (comment)
decentral1se referenced this issue2024-12-21 19:28:13 +00:00
backup-bot-twois quite stable now, hopefully migrating to that is an acceptable fix for this. The soon (hopefully) to be releasedabrawill also support it. Also, I've opened up a discussion to see what we should do forbackup-botin general: coop-cloud/backup-bot#5 Unsure what more can be done, gonna close this now. Feel free to re-open if there is something to handle!