Docker Community Forums

Share and learn in the Docker community.

"Docker has been updated!" Yes, I know


(KnutsenM) #1

Expected behavior

Receive “Docker has been updated!” notification only when Docker has been updated.

Actual behavior

Receive “Docker has been updated!” notification every time Docker runs.

Information

Docker for Mac: version: win-beta-v1.12.0-rc5-beta21-73-g9cd1dc2
OS X: version 10.11.6 (build: 15G31)
logs: /tmp/189FDCBF-7AEB-4B1A-9A1F-35F922015A2D/20160801-101405.tar.gz
[OK] docker-cli
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce the behavior

  1. Quit Docker
  2. Restart Docker
  3. See notification, “Docker has been updated! / New version is 1.12.0”

Note, I switched to stable version from beta by simply downloading it and replacing the .app


(Yallop) #2

Thanks for the report. There’s an issue open for this problem:

https://github.com/docker/for-mac/issues/51


(Occam) #3

Happens to me too. Annoying as hell.


(KnutsenM) #4

In duplicate issue https://github.com/docker/for-mac/issues/169, @dsheets says, “We are working on a fix which will reach the beta channel first and then stable with 1.12.1.”


(KnutsenM) #5

No good; 1.12.1 does the same thing. :frowning:


(KnutsenM) #6

I switched back to the beta channel. The problem appears to be gone in Version 1.12.1-beta26.1 (build: 12100), but I’m not certain if that’s due to the version, or to the channel switch.


(KnutsenM) #7

Whups, the problem has returned with 1.12.2-rc1-beta27


(KnutsenM) #8

I suspect this is related to problems with /Library/PrivilegedHelperTools/com.docker.vmnetd detailed below.

My copy of vmnetd hasn’t changed since I switched back to the beta channel, and it remains running after I quit Docker.




(KnutsenM) #9

The release notes for Version 1.12.2-beta28 (12906) specifically mention:

Fixed an issue where Docker for Mac was incorrectly reported as updated

Indeed, the problem seems to have gone away.