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.
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:
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?
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.
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 Docker.app 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?