fix docker permission issues

[pestotoast]

This should fix #10
The start.sh script of the mastercontainer now runs with root privileges so we can manage group permissions during startup.

I adjusted the supervisor.conf of the mastercontainer so that all other processes still run as www-data, but had some issues with log file permissions, thats why I removed some logging options from the supervisor.conf. (Do we need them?)

[LukasReschke]

@szaimen WDYT? :)

[szaimen]

@pestotoast Thank you for your PR! I just discussed with @LukasReschke that your PR makes sense. I'll test it and update it if needed later on. Please make sure to allow edit by the maintainers for your branch, if not already done. Thanks! :)

[szaimen]

lgtm. I'll test this now on the develop channel

[pestotoast]

Unfortunately those new changes don't work for me. I get a permission denied error now:

[Fri Dec 03 11:48:32.569176 2021] [core:crit] [pid 58] (13)Permission denied: [client 127.0.0.1:43128] AH00529: /var/www/docker-aio/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/var/www/docker-ai
o/' is executable

docker exec -it nextcloud-aio-mastercontainer chown -R root:www-data /var/www/docker-aio seems to fix it though

But after the login I get:

Fatal error: Uncaught GuzzleHttp\Exception\ConnectException: cURL error 7: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://localhost/v1.41/networks/create in /var/www/docker-aio/php/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:210

My guess is that it's another permission error with docker now. Apache still seems to run as www-data, but /var/run/docker.sock now has root:root permissions.

[szaimen]

Yes, thanks for testing! I've just seen the problem, too. Will fix it in #33. Fortunately it isn't deployed to latest, yet.