ae6533484c
Currently on daemon start volumes are "created" which involves invoking a volume driver if needed. If this process fails the mount is left in a bad state in which there is no source or Volume set. This now becomes an unrecoverable state in which that container can not be started. The only way to fix is to restart the daemon and hopefully you don't get another error on startup. This change moves "createVolume" to be done at container start. If the start fails it leaves it in the state in which you can try another start. If the second start can contact the volume driver everything will recover fine. Signed-off-by: Darren Shepherd <darren@rancher.com> Upstream-commit: 2aa673aed7cd10497d578a14a9550c75789e0a43 Component: engine
This directory contains code pertaining to running containers and storing images
Code pertaining to running containers:
- execdriver
Code pertaining to storing images:
- graphdriver