From a19af32f811c6b4276244a85e3c38a69fc409c92 Mon Sep 17 00:00:00 2001 From: Kevin Casey <12061237+kevinjamescasey@users.noreply.github.com> Date: Wed, 2 Oct 2024 21:52:37 -0500 Subject: [PATCH 1/6] Update deploy-intro.html Add note to alert people that the command might not work on their machine depending on the CPU architecture --- .../tutorials/kubernetes-basics/deploy-app/deploy-intro.html | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html b/content/en/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html index 3411ce8f54d0c..364e45b0cf299 100644 --- a/content/en/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html +++ b/content/en/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html @@ -121,6 +121,7 @@
Let’s deploy our first app on Kubernetes with the kubectl create deployment
command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
Let’s deploy our first app on Kubernetes with the kubectl create deployment
command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
Let’s deploy our first app on Kubernetes with the kubectl create deployment
command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
Let’s deploy our first app on Kubernetes with the kubectl create deployment
command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
kubenetes-bootcamp
image is built only for the amd64
CPU architecture and may not work on your machine.{{< /note >}}
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
This tutorial uses a container that requires the AMD64 architecture. If you are using minikube on a computer with a different CPU architecture, you could try using minikube with - a driver that can emulate AMD64. For example, the Docker Desktop driver can do this.
+ a driver that can emulate AMD64. For example, the Docker Desktop driver can do this. You can + make sure Docker Deskstop is running when you issue your first `minikube start` command. If + you already have other Minikube instances you can create a one with `minikube start driver=docker`. {{< /note >}}@@ -121,7 +123,6 @@
Let’s deploy our first app on Kubernetes with the kubectl create deployment
command. We need to provide the deployment name and app image location (include the full repository url for images hosted outside Docker Hub).
kubenetes-bootcamp
image is built only for the amd64
CPU architecture and may not work on your machine.{{< /note >}}
kubectl create deployment kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1
Great! You just deployed your first application by creating a deployment. This performed a few things for you:
This tutorial uses a container that requires the AMD64 architecture. If you are using - minikube on a computer with a different CPU architecture, you could try using minikube with - a driver that can emulate AMD64. For example, the Docker Desktop driver can do this. You can - make sure Docker Deskstop is running when you issue your first `minikube start` command. If - you already have other Minikube instances you can create a one with `minikube start driver=docker`.
+This tutorial uses a container that requires the AMD64 architecture. If you are + using minikube on a computer with a different CPU architecture, you could try using + minikube with a driver that can emulate AMD64. For example, the Docker Desktop + driver can do this after + you install Docker Desktop. You can either make sure Docker Desktop is running when + you issue your first `minikube start` comman; or, if you already have a Minikube + instance, you can create a new one with `minikube start driver=docker`.
{{< /note >}}