My machine experienced a kernel panic today and rebooted. I chose to re-open applications I had running before the panic. Among those were Docker and Kitematic. I had many images built and showing in the output of docker images
but noticed there were all gone after recovering from the panic and reboot.
When my applications were launching after the recovery, I noticed Kitematic mentioned it was starting a Linux VM. I’m starting to wonder if that had an effect on my images.
Expected behavior
Docker images should be available.
Actual behavior
Docker images are missing.
Information
Docker for Mac: version: mac-v1.12.0-beta20
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160721-194025.tar.gz
[OK] docker-cli
[OK] app
[OK] moby-syslog
[OK] virtualization
[OK] menubar
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux
OS X 10.11.5 (15F34)
Client:
Version: 1.12.0-rc4
API version: 1.24
Go version: go1.6.2
Git commit: e4a0dbc
Built: Wed Jul 13 03:28:51 2016
OS/Arch: darwin/amd64
Experimental: true
Server:
Version: 1.12.0-rc4
API version: 1.24
Go version: go1.6.2
Git commit: e4a0dbc
Built: Wed Jul 13 03:28:51 2016
OS/Arch: linux/amd64
Experimental: true
Automatically start Docker when you log in
is enabled
Steps to reproduce the behavior
- Launch Docker.app
docker pull postgres
- Hard shutdown and boot the machine
- Launch Docker.app
-
docker images
still lists postgres - Launch Kitematic (Beta).app
- Hard shutdown and boot the machine
- Elect to re-open applications so Kitematic will launch again
- Kitematic launches and starts a linux VM – Example screenshot
-
docker images
returns no images