From e0be992ec399b3de558c1673ab64cf0d23887c1b Mon Sep 17 00:00:00 2001 From: Emma Date: Thu, 20 May 2021 13:51:29 -0700 Subject: [PATCH 1/2] Update registry.md I recently attempted to follow this guide and ran into two issues. 1. I already had a cluster running when I ran `minikube start --insecure-registry` and as such the insecure registry flag wasn't respected. I needed to run `minikube delete` and then could run the start command. As far as I'm aware the hard reset is only necessary on MacOS. 2. I was confused by the output from `minikube addons enable registry`. There is a big message of `Registry addon with docker driver uses port please use that instead of default port 5000` and so I switched a few things over to the generated port and nothing connected. Retrying with only port 5000 worked successfully. --- site/content/en/docs/handbook/registry.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/site/content/en/docs/handbook/registry.md b/site/content/en/docs/handbook/registry.md index 1d18b6aaf4..1b5113b284 100644 --- a/site/content/en/docs/handbook/registry.md +++ b/site/content/en/docs/handbook/registry.md @@ -42,7 +42,8 @@ You can use the `--insecure-registry` flag on the One nifty hack is to allow the kubelet running in minikube to talk to registries deployed inside a pod in the cluster without backing them with TLS certificates. Because the default service cluster IP is known to be available at 10.0.0.1, users can pull images from registries -deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. +deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. If using macOS, ensure the cluster +is deleted using `minikube delete` before starting with the `--insecure-registry` flag. ### docker on macOS @@ -53,6 +54,7 @@ The first step is to enable the registry addon: ```shell minikube addons enable registry ``` +> Note: Minikube will generate a port and request you use that port when enabling registry. That instruction is not related to this guide. When enabled, the registry addon exposes its port 5000 on the minikube's virtual machine. From c8a6fdfc831c9ef167c84cca6a1df0eaff7721b0 Mon Sep 17 00:00:00 2001 From: Emma Date: Thu, 20 May 2021 16:00:06 -0700 Subject: [PATCH 2/2] Update registry.md Remove the MacOS specific information as it is true for all operating systems --- site/content/en/docs/handbook/registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/en/docs/handbook/registry.md b/site/content/en/docs/handbook/registry.md index 1b5113b284..12995de882 100644 --- a/site/content/en/docs/handbook/registry.md +++ b/site/content/en/docs/handbook/registry.md @@ -42,7 +42,7 @@ You can use the `--insecure-registry` flag on the One nifty hack is to allow the kubelet running in minikube to talk to registries deployed inside a pod in the cluster without backing them with TLS certificates. Because the default service cluster IP is known to be available at 10.0.0.1, users can pull images from registries -deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. If using macOS, ensure the cluster +deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. Ensure the cluster is deleted using `minikube delete` before starting with the `--insecure-registry` flag. ### docker on macOS