Replies: 5 comments 4 replies
-
From my nextcloud container logs:
Is this this problem? Is it safe to remove the network or is this potential deconstructive? |
Beta Was this translation helpful? Give feedback.
-
This fixed my issue on all 3 instances Thanks @szaimen |
Beta Was this translation helpful? Give feedback.
-
Hi, want to ask does AIO need to be run in a network envrioment? I'm in my test enviroment, there's no public network access, and keeps getting this DNS error, |
Beta Was this translation helpful? Give feedback.
-
Problem
For AIO instances that have been initially created between March 9th 2022 and March 24th 2022, upgrading to v4.4.1 or higher might suddenly disable the dns resolution for the AIO containers. This is due to
Internal: true
settings that was falsely applied to the nextcloud-aio network during that time. Now with the update to v4.4.1 we remove the default bridge network which leads to the containers suddenly not being able to do dns resolution anymore.Fix
In order to fix this, you need to do the following:
sudo docker stop $(sudo docker ps --format {{.Names}} | grep '^nextcloud-aio')
sudo docker stop nextcloud-aio-mastercontainer
sudo docker network disconnect nextcloud-aio nextcloud-aio-mastercontainer
sudo docker network rm nextcloud-aio
sudo docker network connect bridge nextcloud-aio-mastercontainer
sudo docker start nextcloud-aio-mastercontainer
Beta Was this translation helpful? Give feedback.
All reactions