Statically set the application name in the init scripts.
This allows the sysvinit scripts to be used at boot time.
Currently the issue is that when you enable docker-volume-netshare with update-rc.d docker-volume-netshare defaults is that it create the symlinks under /etc/rc*.d as such /etc/rc2.d/S20docker-volume-netshare. This in turn causes the script to pickup S20docker-volume-netshare as BASE on boot and so docker-volume-netshare fails to startup with /usr/bin/S20docker-volume-netshare not present or not executable.
This is not visible when doing service docker-volume-netshare start because in this case it uses /etc/init.d/docker-volume-netshare as and picks up docker-volume-netshare as BASE.
Statically set the application name in the init scripts.
This allows the sysvinit scripts to be used at boot time.
Currently the issue is that when you enable docker-volume-netshare with
update-rc.d docker-volume-netshare defaults
is that it create the symlinks under /etc/rc*.d as such/etc/rc2.d/S20docker-volume-netshare
. This in turn causes the script to pickupS20docker-volume-netshare
as BASE on boot and so docker-volume-netshare fails to startup with/usr/bin/S20docker-volume-netshare not present or not executable
.This is not visible when doing
service docker-volume-netshare start
because in this case it uses /etc/init.d/docker-volume-netshare as and picks updocker-volume-netshare
as BASE.