Bug: Supervisord Error and Warning

[3kami3]

Summary

An error (CRIT) and warning (UserWarning) occur and the following message is output.

==> /var/log/supervisor/supervisor.log <==
  self.warnings.warn(
2024-04-03 21:42:44,820 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-04-03 21:42:44,820 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2024-04-03 21:42:44,822 INFO RPC interface 'supervisor' initialized
2024-04-03 21:42:44,822 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-04-03 21:42:44,822 INFO supervisord started with pid 17
2024-04-03 21:42:45,825 INFO spawned: 'ntpd' with pid 19
2024-04-03 21:42:45,826 INFO spawned: 'samba' with pid 20
2024-04-03 21:42:47,113 INFO success: ntpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-03 21:42:47,113 INFO success: samba entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

and

==> /var/log/supervisor/supervisor.log <==
/usr/lib/python3/dist-packages/supervisor/options.py:473: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  self.warnings.warn(
2024-04-03 22:00:47,771 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2024-04-03 22:00:47,771 INFO Set uid to user 0 succeeded
2024-04-03 22:00:47,775 INFO RPC interface 'supervisor' initialized
2024-04-03 22:00:47,775 INFO supervisord started with pid 16
2024-04-03 22:00:48,777 INFO spawned: 'ntpd' with pid 18
2024-04-03 22:00:48,778 INFO spawned: 'samba' with pid 19
2024-04-03 22:00:50,645 INFO success: ntpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-03 22:00:50,645 INFO success: samba entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Steps to reproduce

$ mkdir -p /data/docker/containers/samba/data /data/docker/containers/samba/config/samba
$ docker pull nowsci/samba-domain
$ docker run -t -i \
    -e "DOMAIN=CORP.EXAMPLE.COM" \
    -e "DOMAIN_DC=dc=corp,dc=example,dc=com" \
    -e "DOMAIN_EMAIL=example.com" \
    -e "DOMAINPASS=ThisIsMyAdminPassword^123" \
    -e "DNSFORWARDER=192.168.0.15" \
    -e "HOSTIP=192.168.0.127" \
    -p 192.168.0.127:53:53 \
    -p 192.168.0.127:53:53/udp \
    -p 192.168.0.127:88:88 \
    -p 192.168.0.127:88:88/udp \
    -p 192.168.0.127:123:123 \
    -p 192.168.0.127:123:123/udp \
    -p 192.168.0.127:135:135 \
    -p 192.168.0.127:137-138:137-138/udp \
    -p 192.168.0.127:139:139 \
    -p 192.168.0.127:389:389 \
    -p 192.168.0.127:389:389/udp \
    -p 192.168.0.127:445:445 \
    -p 192.168.0.127:464:464 \
    -p 192.168.0.127:464:464/udp \
    -p 192.168.0.127:636:636 \
    -p 192.168.0.127:1024-1044:1024-1044 \
    -p 192.168.0.127:3268-3269:3268-3269 \
    -v /etc/localtime:/etc/localtime:ro \
    -v /data/docker/containers/samba/data/:/var/lib/samba \
    -v /data/docker/containers/samba/config/samba:/etc/samba/external \
    --dns-search corp.example.com \
    --dns 192.168.0.127 \
    --dns 192.168.0.15 \
    --add-host exampledc.corp.example.com:192.168.0.127 \
    -h exampledc \
    --name samba \
    --privileged \
    nowsci/samba-domain

Expected behavior

2024-04-03 22:06:21,285 INFO Set uid to user 0 succeeded
2024-04-03 22:06:21,287 INFO supervisord started with pid 17
2024-04-03 22:06:22,290 INFO spawned: 'ntpd' with pid 19
2024-04-03 22:06:22,291 INFO spawned: 'samba' with pid 20
2024-04-03 22:06:23,540 INFO success: ntpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-03 22:06:23,540 INFO success: samba entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)