Skip to content
Discussion options

You must be logged in to vote

Why the loop happens (and why the log looks empty after restoring)

In Containers/nextcloud/entrypoint.sh, when Nextcloud AIO runs an update:

  1. It redirects the update output to update.log inside your Nextcloud data directory (exec > >(tee -i "/var/www/html/data/update.log")).
  2. If the update fails, it creates update.failed in $NEXTCLOUD_DATA_DIR and exits on every subsequent container start.
  3. When you restore from backup, AIO creates skip.update so the container starts cleanly on the backed-up version—and the restore overwrites update.log, which is why it looks empty afterward.
  4. Overnight, AIO's scheduled daily backup/update job runs again, sees image_version > installed_version, retries the…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@roelofz
Comment options

Answer selected by szaimen
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants