AIO Mastercontainer stuck in restarting loop

I am on Debian
I set up nextcloud AIO using the standard installation per the readme file on GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All-in-One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.
I installed using my user (not root) with sudo permissions
It was all working fine as of last week but today I couldn’t reach my files per webdav, the url is unreachable and on closer inspection discovered the mastercontainer was in a restarting loop. I stopped other containers per How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub as this resolved a previous issue I had but the mastercontainer remains stuck.

running docker logs for the mastercontainer returns the following repeatedly:

sudo: /etc/sudo.conf is world writable
sudo: /etc/sudo.conf is world writable
sudo: error in /etc/sudo.conf, line 0 while loading plugin “sudoers_policy”
sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
sudo: fatal error, unable to load plugins
Trying to fix docker.sock permissions internally…
Adding internal www-data to group docker
sudo: /etc/sudo.conf is world writable
sudo: /etc/sudo.conf is world writable
sudo: error in /etc/sudo.conf, line 0 while loading plugin “sudoers_policy”
sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
sudo: fatal error, unable to load plugins
Docker socket is not readable by the www-data user. Cannot continue.

I ran some updates on Debian before I noticed the issue but apart from that have done nothing on the server.

The workaround here Docker socket is not readable by the www-data user. · Issue #10 · nextcloud/all-in-one · GitHub
sudo groupmod -g 998 docker has not worked

I have pulled the latest release using docker pull but I assume I have to resolve some issue with permissions and don’t want to break anything in docker without some help. Thanks to all for any assistance!

What are the file permissions and owners of:

/usr/lib/sudo/sudoers.so
/etc/sudo.conf

Any chance you did a chown -R or chmod -R at some point since things last worked?

/usr/lib/sudo/sudoers.so here:
-rw-r--r-- 1 root root 553480 Jan 14 14:29 /usr/lib/sudo/sudoers.so

/etc/sudo.conf here:
-rw-r--r-- 1 root root 3975 Feb 27 2021 /etc/sudo.conf

I mounted the nextcloud instance per webdav to my home directory according to the official nextcloud documentation. This seemed to work. My goal is to access the nextcloud files using emacs, accessing these files through the file system in emacs (dired?) I could open the files there but couldn’t save them, so I did run chown -R and probably chmod -R on the mounted ~/nextcloud directory for my $USER.

Note: this is all on the same server. I couldn’t access the files directly in /var/lib/docker/volumes :permission denied. For good reason I thought, therefore the plan B with webdav which worked fine on another NC instance, since deprecated.