Images, containers disappear after failed attempt to docker push to private registry through VPN

Docker Desktop for Mac
1

Expected behavior

Images, containers do not disappear after attempting to push them through VPN to private registry

Actual behavior

Images, containers disappear after attempting to push them through VPN to private registry

Information

  • the output of:
    • Moby Menu > Diagnose & Feedback on OSX

Docker for Mac: version: abf019d
OS X: version 10.11.6 (build: 15G31)
logs: /tmp/FE1309BB-5514-40D4-875D-E3F1FEF1E87E/20160822-065106.tar.gz
[OK] docker-cli
[OK] dns
[OK] moby-syslog
[OK] app
[OK] disk
[OK] system
[OK] virtualization
[OK] osxfs
[OK] menubar
[OK] db
[OK] slirp
[OK] logs
[OK] moby-console
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

  • a reproducible case if this is a bug, Dockerfiles FTW
  • page URL if this is a docs issue or the name of a man page
  • host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )

(see moby menu diagnosis)

Steps to reproduce the behavior

Note: this is the 4th time this issue has happened with either “stable” or beta DfM, but the first time (noticed) was after failed private registry push through F5 VPN). Should not have “stable” release when this is clearly not ready for prime time.

  1. install either stable or beta DfM
  2. create docker images, normal workflow, e.g.,

$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
mesosphere/dcos-docker base c7e8b8d01a6b 3 days ago 611.5 MB
mesosphere/dcos-docker centos c7e8b8d01a6b 3 days ago 611.5 MB
mesosphere/dcos-docker centos-7 c7e8b8d01a6b 3 days ago 611.5 MB
java 8-jre 0a290b7fd4c4 11 days ago 311.1 MB
alpine 3.4 4e38e38c8ce0 8 weeks ago 4.799 MB

  1. connect to corporate network through F5 BIG-IP Edge Client, version 7101.2015.0224.1
  2. attempt to push to private docker registry - this failed
  3. connect to corporate intranet (not via F5 routed VPN)
  4. images poof gone #docker images

$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
$

  1. (EDIT) this 4th time may be unrelated to previous 3 times images, containers disappeared - before, the ~/Library/Containers would contain something like com.docker.docker with several gig of data (assumed this is where the image binaries were stored) and these would still persist even if docker could not see them. I suspected #docker rmi -f issue with aufs …that a layer was missing that caused failure to see all docker images, even if that image did not depend on that layer. But this is something new - there is no ~/Library/Containers or ~/Library/Group Containers. A coworker suspects it is related to change in file encryption when switching between networks.