minikube: --insecure-registry does not work on an existing VM

minikube version: v1.1.1 operating system version: macOS 10.14

minikube start \
    --docker-env=HTTP_PROXY=$HTTP_PROXY \
    --docker-env=HTTPS_PROXY=$HTTPS_PROXY \
    --docker-env=NO_PROXY=$NO_PROXY \
    --registry-mirror=https://registry.docker-cn.com \
    --insecure-registry="192.168.99.1:5000"

add the option --insecure-registry="192.168.99.1:5000" is newly added. And do minikue stop & start，but the option insecure-registry does not appear in docker info. It will not take effect until do minikube delete and recreate.

I try minikube ssh and use root user edit /etc/docker/daemon.json, then systemctl restart docker, but failed. I got err same as https://github.com/kubernetes/minikube/issues/3800:

Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Is there any convenient way to make it effective?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 16 (6 by maintainers)

Most upvoted comments

I’ve added the insecure registry manually at the machine config file ~/.minikube/machines/<PROFILE_NAME>/config.json and it worked for me.

jorgemoralespou on Dec 4, 2019

I feel like this is because the addon needs the minikube to be restarted, and addon enable wont enable it witrhout stop and restart

medyagh on Dec 16, 2019