探索如何讓 GKE 虛擬機器發揮最佳成本效益 Reviews

Please update the pod definition with containers actually including the shell. Also the last check did not work correctly while "k get pods -o wide" already showed all pods running and on the same node.

Simon M. · Reviewed almost 4 years ago

kubectl exec -it pod-1 -- sh is not working

sachin m. · Reviewed almost 4 years ago

- kubectl exec -it pod-1 -- sh doesn't work - the last check never succeeds

Taku K. · Reviewed almost 4 years ago

Taku K. · Reviewed almost 4 years ago

Piyush R. · Reviewed almost 4 years ago

Pengkuh D. · Reviewed almost 4 years ago

Mohan Krishna A. · Reviewed almost 4 years ago

Basavaraj H. · Reviewed almost 4 years ago

Problem with latest pod 1 image. Also even if you use old images, traffic simulation fails when you can see traffic in logs. Problem with this assignment, can be completed only 90%.

Bhushan N. · Reviewed almost 4 years ago

ALOK K. · Reviewed almost 4 years ago

The command kubectl exec -it pod-1 -- sh wouldn't execute and said error: Internal error occured: error executing command in container: failed to exec in container: failed to start exec "7ab..." It's almost funny how many random occurs occur throughout these qwiklabs making them impossible to get 100% on

Brenden A. · Reviewed almost 4 years ago

Chun-Te S. · Reviewed almost 4 years ago

Amasidda L. · Reviewed almost 4 years ago

Mohit B. · Reviewed almost 4 years ago

Problem with pod 1 exec command. OCI error from gcloud is not allowing me to complete this lab. Taken multiple times. This is container software version issue. Please help correct it.

Bhushan N. · Reviewed almost 4 years ago

Mohan Krishna A. · Reviewed almost 4 years ago

Pushpanjali S. · Reviewed almost 4 years ago

Weichen L. · Reviewed almost 4 years ago

Vignesh R. · Reviewed almost 4 years ago

Boran L. · Reviewed almost 4 years ago

Robin S. · Reviewed almost 4 years ago

Sujnana R. · Reviewed almost 4 years ago

Vivek B. · Reviewed almost 4 years ago

Scale up task: the task expected not having enough resources but actually I had enough. Needed to scale up to 3 pods to receive the expected error message. SH is not available on pod-1: student_02_1f75c7827c27@cloudshell:~ (qwiklabs-gcp-01-97f67d841871)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "3043c4805c0cf0cc7411d94b9a05a249125efbbee04a7e74a7a16e4a2f62f80d": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown But it is available for pod-2: student_02_1f75c7827c27@cloudshell:~ (qwiklabs-gcp-01-97f67d841871)$ kubectl exec -it pod-2 -- sh # ping 10.60.0.9 PING 10.60.0.9 (10.60.0.9): 56 data bytes 64 bytes from 10.60.0.9: icmp_seq=0 ttl=62 time=1.822 ms 64 bytes from 10.60.0.9: icmp_seq=1 ttl=62 time=0.417 ms 64 bytes from 10.60.0.9: icmp_seq=2 ttl=62 time=0.417 ms 64 bytes from 10.60.0.9: icmp_seq=3 ttl=62 time=0.422 ms You cannot ping a port number: # ping 10.60.0.9:8080 ping: unknown host

István A. · Reviewed almost 4 years ago

Tom P. · Reviewed almost 4 years ago