Thank you for the PR. Will this cause issues for people already running as root on upgrade with file permissions? If so, we will need to include a check, or allow supplying of a user on the ENV with default to root so it's not a breaking change.

Thank you for the PR. Will this cause issues for people already running as root on upgrade with file permissions? If so, we will need to include a check, or allow supplying of a user on the ENV with default to root so it's not a breaking change.

Errors and warnings are output in the current latest version, but nothing is specified, so the supervisord process is already running with root privileges.
If I add user=root to the configuration file, the errors and warnings do not occur. I see no effect on file permissions.

Sounds good. Why the addition of the insecure http server? For that to be merged we'd need a good case for it, and it would need to be an option via env along with the credentials.

Sounds good. Why the addition of the insecure http server? For that to be merged we'd need a good case for it, and it would need to be an option via env along with the credentials.

The reason for adding the unix_http_server section is
"CRIT Server 'unix_http_server' running without any HTTP authentication checking".
The solution is based on the following supervisor issue
Supervisor/supervisor#694
Supervisor/supervisor#717 (comment)