Exploring Cost-optimization for GKE Virtual Machines avis
24421 avis
Ablaye F. · Examiné il y a environ 3 ans
Ghada a. · Examiné il y a environ 3 ans
so fuc*ing slow when creating cluster
Arif P. · Examiné il y a environ 3 ans
Arif P. · Examiné il y a environ 3 ans
Arun B. · Examiné il y a environ 3 ans
Brandon C. · Examiné il y a environ 3 ans
Aben Liangliang L. · Examiné il y a environ 3 ans
Chengjie F. · Examiné il y a environ 3 ans
Zhen L. · Examiné il y a environ 3 ans
Rayane B. · Examiné il y a environ 3 ans
The ping command did not work - so not traffic flow logs generated and did not see the data to put into BigQuery. Error : student_00_309e927e62bd@cloudshell:/ (qwiklabs-gcp-03-2389d82927e7)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "91d7a216cbdd72d58d77faded47940c5a20b9ef60381b1a25263e1f600c61d9e": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown I had lots of problems during this lab - I have tried it twice.
Sunny L. · Examiné il y a environ 3 ans
Tomek J. · Examiné il y a environ 3 ans
running sh on the pod does not work
Lautaro Alejandro B. · Examiné il y a environ 3 ans
Ablaye F. · Examiné il y a environ 3 ans
pod1 uses distroless, so it no longer has `sh`, the format for `ping` does not include the port, so `:8080` is just confusing, does not work.
Gabor B. · Examiné il y a environ 3 ans
Eduardo P. · Examiné il y a environ 3 ans
Yuan Jian P. · Examiné il y a environ 3 ans
Rodnei M. · Examiné il y a environ 3 ans
The ping command did not work - so not traffic flow logs generated and did not see the data to put into BigQuery. Error : student_00_309e927e62bd@cloudshell:/ (qwiklabs-gcp-03-2389d82927e7)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "91d7a216cbdd72d58d77faded47940c5a20b9ef60381b1a25263e1f600c61d9e": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
Sunny L. · Examiné il y a environ 3 ans
The ping command did not work - so not traffic flow logs generated and did not see the data to put into BigQuery. Error : student_00_309e927e62bd@cloudshell:/ (qwiklabs-gcp-03-2389d82927e7)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "91d7a216cbdd72d58d77faded47940c5a20b9ef60381b1a25263e1f600c61d9e": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
Sunny L. · Examiné il y a environ 3 ans
The ping command did not work - so not traffic flow logs generated and did not see the data to put into BigQuery. Error : student_00_309e927e62bd@cloudshell:/ (qwiklabs-gcp-03-2389d82927e7)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "91d7a216cbdd72d58d77faded47940c5a20b9ef60381b1a25263e1f600c61d9e": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
Sunny L. · Examiné il y a environ 3 ans
Peramala V. · Examiné il y a environ 3 ans
Iurii G. · Examiné il y a environ 3 ans
Mikias Mesfin B. · Examiné il y a environ 3 ans
not able to create hello server
Mikias Mesfin B. · Examiné il y a environ 3 ans
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.