Docker Mac Beta using insecure Private Registry

I am using Docker version 1.11.1, build 5604cbe on Mac OS X

On my Mac machine I am trying to do docker push to private docker registry running on remote VM. I am unable to get SSL to work and want to use insecure registry following instructions on How Can I specify DOCKER_OPTS on my Mac so I can push the image to private registry?

  • CrashLoopBackOff when args are added in Kubernetes
  • Workers dying early due to uneven work distribution in Luigi (2.6.1)
  • starting container using docker API
  • Docker-compose specify config file
  • Docker's NAT table output chain rule
  • “Filename too long” in sbt assembly inside a docker container
  • Failing to execute nginx proxy_pass directive for a Dancer2 app inside a Docker container
  • Store and Restore Inherited Dockerfile USER setting
  • How can i execute commands inside containers during host provision
  • Running Visual Studio Remote Debugger in Windows Container (Docker managed)
  • How mount subdirectory in mounted directory in Docker?
  • Datanode denied communication with namenode because hostname cannot be resolved
  • 3 Solutions collect form web for “Docker Mac Beta using insecure Private Registry”

    In case other people are having the same Get x509: certificate signed by unknown authority problem, I’ve posted a simple solution on my blog: it all boils down, as @manojlds has pointed out, to whitelisting the server in the Advanced preferences.

    I got the response on docker forums –

    pinata set daemon '{"storage-driver":"aufs","debug":true,"insecure-registries":[""]}'

    Pinata has been removed from more recent versions. You can setup insecure registries from Preferences -> Advanced.

    Currently there is no official CLI based way to do the update.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.