Note you will see the following warning when rsync is installed (as a dependency of git).
Setting up rsync (3.1.0-2ubuntu0.1) ...
Removing any system startup links for /etc/init.d/rsync ...
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match rsync Default-Stop values (none)
Adding system startup for /etc/init.d/rsync ...
/etc/rc0.d/K20rsync -> ../init.d/rsync
/etc/rc1.d/K20rsync -> ../init.d/rsync
/etc/rc6.d/K20rsync -> ../init.d/rsync
/etc/rc2.d/S20rsync -> ../init.d/rsync
/etc/rc3.d/S20rsync -> ../init.d/rsync
/etc/rc4.d/S20rsync -> ../init.d/rsync
/etc/rc5.d/S20rsync -> ../init.d/rsync
invoke-rc.d: policy-rc.d denied execution of restart.
This is due to /usr/sbin/policy-rc.d not allowing restart of services. I don't think this will have any effect since we know we are creating a docker image and not restarting services to a clean state on apt-get install of the service.
Note you will see the following warning when rsync is installed (as a dependency of git).
This is due to /usr/sbin/policy-rc.d not allowing restart of services. I don't think this will have any effect since we know we are creating a docker image and not restarting services to a clean state on apt-get install of the service.
You can see more about this general issue here: http://askubuntu.com/questions/226227/how-to-manually-restart-services-affected-by-apt-upgrades