-
Steps to reproduce
Expected behaviorIt should work as it has every other time. Actual behaviorMaster container has started... but the logs for the container are these Adding internal www-data to group ping It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! Other informationHost OSUbuntu 24.04 Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi,
This is the problem. It needs to be |
Beta Was this translation helpful? Give feedback.
Hi,
This is the problem. It needs to be
-v nextcloud_aio_mastercontainer:/mnt/docker-aio-config.