[program:docker-<%= @title %>]
command=docker start -a fuel-core-<%= @release %>-<%= @title %>
numprocs=1
numprocs_start=0
priority=30
autostart=true
autorestart=true
startsecs=10
startretries=1000000
exitcodes=0,2
stopsignal=KILL
stopwaitsecs=60
redirect_stderr=true
stdout_logfile=/var/log/%(program_name)s.log
stdout_logfile_maxbytes=50MB
stdout_logfile_backups=10
stdout_capture_maxbytes=0
stdout_events_enabled=false
stderr_logfile=/var/log/%(program_name)serr.log
stderr_logfile_maxbytes=50MB
stderr_logfile_backups=10
stderr_capture_maxbytes=0
stderr_events_enabled=false
serverurl=AUTO


[program:docker-<%= @title %>]
command=dockerctl -V <%= @release %> start <%= @title %> --attach
numprocs=1
numprocs_start=0
priority=30
autostart=true
autorestart=true
startsecs=10
startretries=1000000
exitcodes=0,2
stopsignal=KILL
stopwaitsecs=60
redirect_stderr=true
stdout_logfile=/var/log/%(program_name)s.log
stdout_logfile_maxbytes=50MB
stdout_logfile_backups=10
stdout_capture_maxbytes=0
stdout_events_enabled=false
stderr_logfile=/var/log/%(program_name)serr.log
stderr_logfile_maxbytes=50MB
stderr_logfile_backups=10
stderr_capture_maxbytes=0
stderr_events_enabled=false
serverurl=AUTO


Use dockerctl start for supervisorctl container launch
Use dockerctl start for supervisorctl container launch

If docker daemon is restarted, the mount points are not safely
torn down. dockerctl cleans these up before trying to start
the container and therefore should be used.

There was an original change to use direct docker commands
because you could not start a container from a different
Fuel release, but now this is possible and works. Therefore,
this patch depends on the patch that fixes it.

Depends-On: Ia864b0a9843f927aa85945e5ab0b2da4bec3a440
Change-Id: Ie3e471d1c394fac9228b7e2bf4b6877775680b3b
Closes-Bug: #1511294
