Opiniones sobre Migrate to Containers: Qwik Start
Cargando…
No se encontraron resultados.

    Opiniones sobre Migrate to Containers: Qwik Start

    4229 opiniones

    Jonathan C. · Se revisó hace casi 4 años

    Dheeraj C. · Se revisó hace casi 4 años

    Dheeraj C. · Se revisó hace casi 4 años

    Fabio E. · Se revisó hace casi 4 años

    Saurabh S. · Se revisó hace casi 4 años

    Francesco S. · Se revisó hace casi 4 años

    The laboratory is wrong, you can perform the same following the following guide: Link: https://cloud.google.com/migrate/anthos/docs/quickstart

    Pablo R. · Se revisó hace casi 4 años

    The laboratory has a failure, after the migration the port 80 of the pod = source-vm does not work Failed to pull image "source-vm": rpc error: code = Unknown desc = Error response from daemon: pull access denied for source-vm, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Back-off pulling image "source-vm" Error: ImagePullBackOff Error: ErrImagePull (base) MacBook-Pro-de-ifix:vagrant-google pablo$ ping -c 3 35.188.49.222 PING 35.188.49.222 (35.188.49.222): 56 data bytes 64 bytes from 35.188.49.222: icmp_seq=0 ttl=100 time=182.455 ms 64 bytes from 35.188.49.222: icmp_seq=1 ttl=100 time=186.553 ms 64 bytes from 35.188.49.222: icmp_seq=2 ttl=100 time=185.471 ms --- 35.188.49.222 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 182.455/184.826/186.553/1.734 ms (base) MacBook-Pro-de-ifix:vagrant-google pablo$

    Pablo R. · Se revisó hace casi 4 años

    Nikhila M. · Se revisó hace casi 4 años

    Fernando d. · Se revisó hace casi 4 años

    The laboratory has a failure, after the migration the port 80 of the pod = source-vm does not work Failed to pull image "source-vm": rpc error: code = Unknown desc = Error response from daemon: pull access denied for source-vm, repository does not exist or may require 'docker login': denied: requested access to the resource is denied Back-off pulling image "source-vm" Error: ImagePullBackOff Error: ErrImagePull (base) MacBook-Pro-de-ifix:vagrant-google pablo$ ping -c 3 35.188.49.222 PING 35.188.49.222 (35.188.49.222): 56 data bytes 64 bytes from 35.188.49.222: icmp_seq=0 ttl=100 time=182.455 ms 64 bytes from 35.188.49.222: icmp_seq=1 ttl=100 time=186.553 ms 64 bytes from 35.188.49.222: icmp_seq=2 ttl=100 time=185.471 ms --- 35.188.49.222 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 182.455/184.826/186.553/1.734 ms (base) MacBook-Pro-de-ifix:vagrant-google pablo$

    Pablo R. · Se revisó hace casi 4 años

    The laboratory has a failure, after the migration the port 80 of the pod = source-vm does not work Error: Could not connect to Cloud Shell on port 8080. Ensure your server is listening on port 8080 and try again. (base) MacBook-Pro-de-ifix:vagrant-google pablo$ ping -c 3 35.188.49.222 PING 35.188.49.222 (35.188.49.222): 56 data bytes 64 bytes from 35.188.49.222: icmp_seq=0 ttl=100 time=182.455 ms 64 bytes from 35.188.49.222: icmp_seq=1 ttl=100 time=186.553 ms 64 bytes from 35.188.49.222: icmp_seq=2 ttl=100 time=185.471 ms --- 35.188.49.222 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 182.455/184.826/186.553/1.734 ms (base) MacBook-Pro-de-ifix:vagrant-google pablo$

    Pablo R. · Se revisó hace casi 4 años

    student_04_e99939a4c302@cloudshell:~ (qwiklabs-gcp-04-1991c61dc78c)$ kubectl get service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.3.240.1 <none> 443/TCP 37m my-service LoadBalancer 10.3.252.90 34.68.94.41 80:31980/TCP 21m source-vm ClusterIP None <none> <none> 21m No inicia el my-service

    Pablo R. · Se revisó hace casi 4 años

    trojen i. · Se revisó hace casi 4 años

    Alejandro H. · Se revisó hace casi 4 años

    Sunil R. · Se revisó hace casi 4 años

    Shoazali S. · Se revisó hace casi 4 años

    Audrey G. · Se revisó hace casi 4 años

    wrong image tag in deployment_spec.yaml

    David C. · Se revisó hace casi 4 años

    KISHOR K. · Se revisó hace casi 4 años

    there seems to be a problem with pulling the source-vm image from GCR.IO -- adding the SHA does the trick.

    Marcel T. · Se revisó hace casi 4 años

    Marcel T. · Se revisó hace casi 4 años

    Marcel T. · Se revisó hace casi 4 años

    Vinit Anishkumar M. · Se revisó hace casi 4 años

    Yoav M. · Se revisó hace casi 4 años

    No garantizamos que las opiniones publicadas provengan de consumidores que hayan comprado o utilizado los productos. Google no verifica las opiniones.