Pinata missing in latest Mac Beta 1.11.2-beta15

Expected behavior

The pinata command to exist at /Applications/

Actual behavior

The pinata command does not exist at /Applications/


Diagnostic ID: 35986E3F-98B6-48B7-980D-17CD3AE06B3C

Steps to reproduce the behavior

  1. Run the Docker Beta happily.
  2. Upgrade to mac-v1.11.2-beta15
  3. Happiness becomes bounded, joy is fettered.

Looks like some of those configuration options are now available in the Beta Preferences, but not all :frowning:

1 Like

Even if all of the configuration options are added to the UI it is still nice to have a command line tool.


Thanks for the feedback.

This is intended, and I am sorry it annoys you.
The pinata executable was a temporary thing and we are working on providing a nice UI for those options in the Preferences panel.

What pinata options are you lacking the most please?
Feel free to give details about your usage of it. This helps us prioritize tasks. :slight_smile:

1 Like

Does that imply that there will only be a graphical UI or would it still make sense to have a CLI tool?

That’s right.
For now, we don’t plan to provide a CLI tool for changing Docker for Mac settings.

How can we set common daemon options like --bip, --dns, and --dns-search? This worked well with pinata.

1 Like

This is unfortunate.

Looks like the daemon.json now lives @ ~/Library/Containers/com.docker.docker/Data/database/com.docker.driver.amd64-linux/etc/docker/daemon.json
which maps to /Database/branch/master/ro/com.docker.driver.amd64-linux/etc/docker/ inside the VM.

From a screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty session:

✓ Process docker running: /usr/bin/docker daemon --pidfile=/run/ -H tcp:// -H unix:///var/run/docker.sock --config-file=/Database/branch/master/ro/com.docker.driver.amd64-linux/etc/docker/daemon.json --userland-proxy-path /sbin/proxy

1 Like

Docker daemon options will be available from the Preferences panel.
We already added a couple of them.

Thanks for your patience.

Another useful option would be to set SSL certificates for the docker daemon and also for private registries.

eg: /etc/docker/certs.d/myregisry:port/*.crt

Also, the CLI tool for settings is greatly appreciated when managing 10+ machines with scripts.

@gaetan Will Docker for Mac add preferences for most (all?) daemon options?

actually I’d like to change networking to NAT, how can I do it?

1 Like

This seems a serious regression in usability for setting up dev machines with Docker for Mac, using things like Boxen or chef-solo to set daemon options like --bip or --dns, which used to be possible with pinata.

Has there been thought on this use case for a post pinata configuration?


What is a good way to adjust the Docker VM settings and also tell if the Docker for beta app is installed from a shell?

Surely of all people, docker developers would realize the benefits of a declarative definition and a command line tool.

A huge use-case for pinata was switching between different settings for different projects. I even wrote a script that would backup the current config and load a new config for the current project.

As mentioned above, another major use-case is automated tools for dev environments.



Will Docker for Mac add preferences for most (all?) daemon options2?

That is our goal.

@yangwao NAT networking option is not available with Docker for Mac

in other words: automated configuration won’t be possible anymore? Or have you thought about some other way to not be dependent on a GUI in the final release?


This seems to be being overwritten by the binary. The base daemon.json is string in the binary. It seems to replace the file on every restart of the VM. Have you found a way to get around this?