Extreme Instability Since Latest Update to Version 17.12.0-ce-mac55 (23011)

[Miserlou]

Docker For Mac has become unusably unstable since the latest update.

It is constantly restarting by itself, and often it just crashes and disappears.

Information

38D14D7F-9A35-4074-82F3-3D3AF04259E2

Docker for Mac: version: 17.12.0-ce-mac55 (18467c0ae7afb7a736e304f991ccc1a61d67a4ab)
macOS: version 10.13.2 (build: 17C88)
logs: /tmp/38D14D7F-9A35-4074-82F3-3D3AF04259E2/20180314-102856.tar.gz
[OK]     vpnkit
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     app
[OK]     virtualization VT-X
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     moby-console
[OK]     osxfs
[OK]     logs
[OK]     docker-cli
[OK]     disk

Related:

I suspect that this is related: #1941

[Miserlou]

It's noon, I have had three crashes since 9AM today.

[Miserlou]

Related: #2691

[akimd]

Hi @djs55! There are tons of

2018-03-13 10:56:35.381684-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:35.381751-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:35.382297-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:35.382375-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:35.383627-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:35.383694-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:35.386283-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:35.386570-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.905683-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.905782-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.906365-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.906427-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.907068-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.907140-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.907697-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.907762-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.909238-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.909327-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:36.912518-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:36.912576-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts
2018-03-13 10:56:38.434055-0400  localhost vpnkit[21502]: DNS: localhost is ::1 in in /etc/hosts
2018-03-13 10:56:38.434149-0400  localhost vpnkit[21502]: DNS: localhost is 127.0.0.1 in in /etc/hosts

in the logs. Any idea what might make vpnkit so verbose?

[akimd]

You have many logs like this:

2018-03-13 10:32:46.721839-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container 6de34312daeb24c2ce3fac39e13c898a92a5de44593485db29dbde510492b8c6 not registered"}
2018-03-13 10:32:48.443754-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container a66bcf77bec9fd1c727615a755247935a7ac4ab1f93f4eb2885157ae6395d3af not registered"}
2018-03-13 10:32:50.181647-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container 15501c8258c89d33d3b829a26e6f6edc086dbb14f97fdffab757336f35f4655a not registered"}
2018-03-13 10:32:51.770042-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container 90b5ad42ff9cc635f6d96f998c5617715f3a23a0e05453e59fe73413a031c4cd not registered"}
2018-03-13 10:32:53.429834-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container 86352d72d5276835068779f5d52cce2db45a7ee3be734db2cca88a07a06207d0 not registered"}
2018-03-13 10:32:55.281848-0400  localhost com.docker.driver.amd64-linux[13454]: Failed to remove resource on container die: &errors.errorString{s:"Unmount error: container e7eb7958057f9c6ae1266b045802f624e9476604c62797f0c4906eb3277147c1 not registered"}

I also see that your disk image is in raw format, and we found (the hard way) that its support in macOS 10.13.3, err, could use improvements. I recommend starting anew. Docker for Mac will now use (again) the qcow2 format.

[djs55]

I've made a PR to remove the unnecessary DNS logging from vpnkit: [moby/vpnkit#369]

[Miserlou]

I'm not quite sure what you specifically mean by 'starting anew' - does that mean remake my images? Uninstall/reinstall Docker for Mac? Is there a specific file I can delete to use the qcowc rather than raw?

[guillaume-eb]

you can go to Docker preferences, then click the "Reset" option in the menu, and then "Reset to factor defaults".
You will lose all your docker images, containers and volumes, but it will switch back to the qcow2 disk format (you should see it in the preferences disk tab after the reset, in the file name extension).

[akimd]

@Miserlou have you managed to get Docker for Mac back on its feet?

[Miserlou]

Yeah, I reset to factory defaults and raised my RAM allocation and haven't had any stability issues since. Thanks for your help!

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked