when use "boot2docker poweroff" , later "boot2docker up", effect on docker containers running @ time of poweroff? docker pause/docker unpause or docker stop/docker start?
and, when reboot host, assume boot2docker poweroff me? when os starts (mac or windows), "boot2docker up" me?
experimentation shows
"boot2docker poweroff" , "boot2docker up" "docker stop" without "docker start"
"boot2docker down" , "boot2docker up" "docker pause" , "docker unpause"
is there way change "up" behavior?
i tested these scenarios , here finding:
irrespective of how stop boot2docker (i.e. boot2docker stop/halt/down or boot2docker poweroff), there no action equivalent docker pause , docker unpause.
the running containers gets stopped (exited (0)) , if haven't set restart policy in docker, remain stopped.
here list of boot2docker commands , alias may further you.
boot2docker down/stop/halt sends acpi shutdown signal virtualbox boot2docker poweroff sends power off signal virtualbox.
on other hand, boot2docker suspend/save save memory states , saves container states if performed docker pause/unpause. i.e. if containers running before performing boot2docker suspend/save, remain running after command well.
hope helped.
Comments
Post a Comment