Docker Community Forums

Share and learn in the Docker community.

Docker spamming Console


(Camjn) #1

Expected behavior

Fewer logs

Actual behavior

every 10s:
<timestamp1> taskgated[<pid1>]: no application identifier provided, can’t use provisioning profiles [pid=<pid2>]

Information

Diagnostic: 006463EE-EFD6-48A6-A95C-17915126E982
Host: OS X 10.11.6 (15G31)

Steps to reproduce the behavior

  1. start docker for mac
  2. open console.app

(Gautaz) #2

I’m also experiencing the same behavior.

Here is my diagnostic ID:
0420D682-15A3-4205-AF93-919F73633E09

I’ve finally found that docker for mac was causing the logs:

27/07/2016 19:31:06,460 taskgated[523]: no application identifier provided, can't use provisioning profiles [pid=15835]

and PID 15835 was:

15835 ??         0:00.00 /Applications/Docker.app/Contents/Resources/bin/com.docker.frontend {"action":"vmstateevent","args":{"vmstate":"running"}}

It’s hard to trace the pid as the process is rapidly killed (while true; do sudo ps -wax >> ps.log; done at the rescue)


(Aphoid) #3

I see this same behavior on OSX 10.11.6 with the 1.12 beta 20.

$ docker --version
Docker version 1.12.0-rc4, build e4a0dbc, experimental

Console log:

7/28/16 1:47:22.953 PM taskgated[371]: no application identifier provided, can’t use provisioning profiles [pid=56693]
7/28/16 1:47:23.065 PM taskgated[371]: no application identifier provided, can’t use provisioning profiles [pid=56694]

time-correlated ps -ax:

56693 ?? 0:00.04 /Applications/Docker.app/Contents/Resources/bin/com.docker.frontend {“action”:“vmstateevent”,“args”:{“vmstate”:“running”}}
56694 ?? 0:00.04 /Applications/Docker.app/Contents/Resources/bin/com.docker.frontend {“action”:“vmstateevent”,“args”:{“vmstate”:“running”}}


(Spyder) #4

I’m seeing this in both the current beta and the 1.12.0 stable release. It’s taken me a few days to track down what app was causing it!


(Sonarun) #5

I am getting this as well.

Version 1.12.0-beta21 (build: 10868)


(R.F. Pels) #6

Same bahviour has been observed here: Version 1.12.0-beta21 (build: 11019)


(Minir4id) #7

Version 1.12.0-a (build: 11213), stable release would meet this problem too.


(David Sheets) #8

I believe this issue was fixed in Beta 22 and will reach the stable channel in 1.12.1 in a few weeks.


(Kenahoo) #9

I’ve got 1.12.1 installed via Homebrew, and I’m still seeing these messages in the Console.


(David Sheets) #10

@kenahoo What version of Docker for Mac are you running? The Docker for Mac versions track the Docker engine versions but Docker for Mac 1.12.1 hasn’t been released yet (it is still in QA). There should be a Docker for Mac 1.12.1 release within the week.


(Kenahoo) #11

Sorry, it looks like I got confused between brew cask install docker and brew install docker. So here’s what I have installed:

% docker --version
Docker version 1.12.0, build 8eab29e

% brew cask info docker
docker: 1.12.0.11213
https://www.docker.com/products/docker
/usr/local/Caskroom/docker/1.12.0.11213 (68B)
From: https://github.com/caskroom/homebrew-cask/blob/master/Casks/docker.rb
==> Name
Docker for Mac
==> Artifacts
Docker.app (app)

The non-cask install of docker (which I don’t have installed) is at 1.12.1:

% brew info docker     
docker: stable 1.12.1 (bottled), HEAD
Pack, ship and run any application as a lightweight container
https://www.docker.com/
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/docker.rb
==> Dependencies
Build: go ✘
==> Options
--with-experimental
	Enable experimental features
--without-completions
	Disable bash/zsh completions
--HEAD
	Install HEAD version

(Erikdhansen) #12

Nice – this totally helped me figure out that I was having this exact same problem.