-
|
I get an error most days when the backup is run and the containers all start booting up: I think that OnlyOffice takes so long to start up that the Nextcloud container runs a check to see if the OnlyOffice container is ready before it's ready. When it fails the check it silently disables the OnlyOffice apps until I go into Administrative Settings/ONLYOFFICE and hit the Save button to rerun the check. Then OnlyOffice works fine. How can I fix this behavior? Or is it best fixed in programming? Can I add a startup delay to the Nextcloud container? I don't know Docker well enough to add such a setting myself. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi, there is a startup delay before the --check command is run: The slepp only starts after the nextcloud container was completely started, so usually this should be enough time especially since the nextcloud container waits for onlyoffice to start: all-in-one/Containers/nextcloud/entrypoint.sh Line 675 in a582967 |
Beta Was this translation helpful? Give feedback.
Hi, there is a startup delay before the --check command is run:
all-in-one/Containers/nextcloud/run-exec-commands.sh
Line 3 in a582967
The slepp only starts after the nextcloud container was completely started, so usually this should be enough time especially since the nextcloud container waits for onlyoffice to start:
all-in-one/Containers/nextcloud/entrypoint.sh
Line 675 in a582967