in windows8.1, boot2docker , when virtualbox restart , my gitlab congtainer can not start up

hi , i am use boot2docker with version 1.6.2.
after install it .
i double click the Oracle VM VirtualBox and run boot2docker-vm.
works very well.
then i begin use docker pull sameersbn/gitlab:latest images by powershell .
everything seems very well.
i run my container well and i can visit gitlab in browser whih pubulished port .
good !!
i thought i am done.
but !!
when i shutdown the boot2docker-vm and run it again and then i use docker start command to start my container with name . eg: docker run gitlab

the problem is i can not start it .
here is the docker logs gitlab :
docker@boot2docker:~$ docker logs -f gitlab
Creating satellites...
Starting supervisord...
2015-06-03 05:29:20,380 CRIT Supervisor running as root (no user in config file)
2015-06-03 05:29:20,380 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
2015-06-03 05:29:20,380 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
2015-06-03 05:29:20,380 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
2015-06-03 05:29:20,380 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
2015-06-03 05:29:20,381 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
2015-06-03 05:29:20,392 INFO RPC interface 'supervisor' initialized
2015-06-03 05:29:20,392 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-06-03 05:29:20,392 INFO supervisord started with pid 1
2015-06-03 05:29:21,394 INFO spawned: 'sidekiq' with pid 247
2015-06-03 05:29:21,395 INFO spawned: 'unicorn' with pid 248
2015-06-03 05:29:21,396 INFO spawned: 'cron' with pid 249
2015-06-03 05:29:21,397 INFO spawned: 'nginx' with pid 250
2015-06-03 05:29:21,410 INFO spawned: 'sshd' with pid 251
2015-06-03 05:29:23,296 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startse
cs)
2015-06-03 05:29:23,296 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startse
cs)
2015-06-03 05:29:23,296 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-06-03 05:29:23,297 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs
)
2015-06-03 05:29:23,297 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-06-03 06:26:58,340 WARN received SIGTERM indicating exit request
2015-06-03 06:26:58,341 INFO waiting for cron, nginx, sshd, sidekiq, unicorn to die
2015-06-03 06:26:58,341 INFO stopped: sshd (exit status 0)
2015-06-03 06:26:58,344 INFO stopped: nginx (exit status 0)
2015-06-03 06:26:58,344 INFO stopped: cron (terminated by SIGTERM)
2015-06-03 06:26:58,752 INFO stopped: unicorn (exit status 0)
2015-06-03 06:27:00,083 INFO stopped: sidekiq (exit status 0)
invoke-rc.d: policy-rc.d denied execution of restart.
mv: cannot stat '/etc/ssh/ssh_host_key': No such file or directory
mv: cannot stat '/etc/ssh/ssh_hostkey.pub': No such file or directory
invoke-rc.d: policy-rc.d denied execution of restart.
mv: cannot stat '/etc/ssh/ssh_hostkey': No such file or directory
mv: cannot stat '/etc/ssh/ssh_hostkey.pub': No such file or directory
invoke-rc.d: policy-rc.d denied execution of restart.
mv: cannot stat '/etc/ssh/ssh_hostkey': No such file or directory
mv: cannot stat '/etc/ssh/ssh_host_key.pub': No such file or directory

i tryed the boot2docker with the version 1.5.0 . same problem.
any ideas?

Start by reproducing the restart sequence with boot2docker and the docker start command, then inspect docker logs gitlab and the recorded SSH-key errors. Compare the container's behavior before and after the VM restart; done means the existing GitLab container starts successfully without those errors.