From 904433199597c22d7b198591da7bad6e24832bc3 Mon Sep 17 00:00:00 2001 From: Sven Schober Date: Sat, 17 Apr 2021 22:59:40 +0200 Subject: [PATCH] add note for failing echoserver image on m1 As was discussed in https://github.com/kubernetes/minikube/issues/11107# on m1-based machines the `echoserver:1.4` (and any other available version) does not start. This commit adds a hint for people experiencing this, and links to the issue where a work around is mentioned. --- site/content/en/docs/start/_index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/site/content/en/docs/start/_index.md b/site/content/en/docs/start/_index.md index 900141187ff7..c20a9009c850 100644 --- a/site/content/en/docs/start/_index.md +++ b/site/content/en/docs/start/_index.md @@ -176,6 +176,9 @@ It may take a moment, but your deployment will soon show up when you run: kubectl get services hello-minikube ``` +> :warning: On M1-based machines (`arm64` architecture) the `echoserver:1.4` image currently fails to start. +> Your best bet is to build a custom `echoserver` image and deploy that as is outlined in [#11107](/../../issues/11107#). + The easiest way to access this service is to let minikube launch a web browser for you: ```shell