feat(container): initial dockerfile and settings

!1

includes/etc/supervisor/conf.d/named.conf

@@ -0,0 +1,9 @@
+[program:bind]
+startsecs=0
+stopwaitsecs=55
+command=/usr/sbin/named -c /etc/bind/named.conf
+autorestart=true
+autostart=true
+stdout_logfile=/var/log/supervisor_%(program_name)s.log
+stderr_logfile=/var/log/supervisor_%(program_name)s.log
+retry=3

includes/etc/supervisor/supervisord.conf

@@ -0,0 +1,34 @@
+
+[unix_http_server]
+file=/var/run/supervisor.sock   ; (the path to the socket file)
+chmod=0700                       ; sockef file mode (default 0700)
+
+;[inet_http_server]
+;port = :9001
+; username = user
+; password = 123
+
+[supervisord]
+logfile=/var/log/supervisord.log ; (main log file;default $CWD/supervisord.log)
+pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
+childlogdir=/var/log            ; ('AUTO' child log dir, default $TEMP)
+nodaemon = true
+user=root
+
+; the below section must remain in the config file for RPC
+; (supervisorctl/web interface) to work, additional interfaces may be
+; added by defining them in separate rpcinterface: sections
+[rpcinterface:supervisor]
+supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
+
+[supervisorctl]
+serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket
+
+; The [include] section can just contain the "files" setting.  This
+; setting can list multiple files (separated by whitespace or
+; newlines).  It can also contain wildcards.  The filenames are
+; interpreted as relative to this file.  Included files *cannot*
+; include files themselves.
+
+[include]
+files = /etc/supervisor/conf.d/*.conf