you are still trying to pull the image from google repo, did u install
docker? does "docker images" show u the image that u are trying to intall?
El lunes, 11 de julio de 2016, 10:16:25 (UTC-5), Zuhaa escribió:
>
> This is how `kubectl get events' and 'kubectl logs' look like:
>
> kubectl get event | grep spark6
> 8m 1h 4 spark6-4023296624-djxit Pod
> Warning FailedSync {kubelet minikubevm} Error syncing pod,
> skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image
> pull failed for gcr.io/google_containers/pause-amd64:3.0, this may be
> because there are no credentials on this request. details: (Error response
> from daemon: Get https://gcr.io/v1/_ping: dial tcp 66.102.1.82:443: i/o
> timeout)"
> 59m 59m 1 spark6-4023296624-djxit Pod
> Warning FailedSync {kubelet minikubevm} Error syncing pod,
> skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image
> pull failed for gcr.io/google_containers/pause-amd64:3.0, this may be
> because there are no credentials on this request. details: (Error response
> from daemon: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on
> 10.0.2.3:53: read udp 10.0.2.15:57421->10.0.2.3:53: i/o timeout)"
> 39m 39m 1 spark6-4023296624-djxit Pod
> Warning FailedSync {kubelet minikubevm} Error syncing pod,
> skipping: failed to "StartContainer" for "POD" with ErrImagePull: "image
> pull failed for gcr.io/google_containers/pause-amd64:3.0, this may be
> because there are no credentials on this request. details: (Error response
> from daemon: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on
> 10.0.2.3:53: read udp 10.0.2.15:49759->10.0.2.3:53: i/o timeout)"
> 7m 16m 3 spark6-4023296624-djxit Pod
> Warning FailedSync {kubelet minikubevm} Error syncing pod,
> skipping: failed to "StartContainer" for "POD" with ImagePullBackOff:
> "Back-off pulling image \"gcr.io/google_containers/pause-amd64:3.0\
> <http://gcr.io/google_containers/pause-amd64:3.0%5C>""
>
> kubectl logs spark6-4023296624-djxit
>
> Error from server: container "spark6" in pod "spark6-4023296624-djxit" is
> waiting to start: ContainerCreating
>
>
>
> On Monday, July 11, 2016 at 4:01:49 PM UTC+2, Paul mb wrote:
>>
>> what does the "kubectl get events" tells u, and "kubectl logs podname"
>>
>>
>> El lunes, 11 de julio de 2016, 8:58:05 (UTC-5), Zuhaa escribió:
>>>
>>> Thank you for your reply. As per your suggestion I have pulled and saved
>>> few docker images. I am trying to do 'kubectl run --image=3b8d91fe7572' and
>>> now the status is 'Container Creating'. Do you know how to fix this?
>>>
>>> On Monday, July 11, 2016 at 3:45:03 PM UTC+2, Paul mb wrote:
>>>>
>>>> that repo gcr.io/google-containers/
>>>> <http://gcr.io/google-containers/echoserver:1.4> is for users with an
>>>> account in google cloud(where instead of google_containers, the id of ur
>>>> gcloud project would be there), u should just install docker and build the
>>>> image from there and pull it for kubernetes locally
>>>> El lunes, 11 de julio de 2016, 5:17:56 (UTC-5), Zuhaa escribió:
>>>>>
>>>>> I have installed Kubernetes in Ubuntu server using instructions here
>>>>> <https://github.com/kubernetes/minikube/blob/master/README.md>. I am
>>>>> trying to create pods using `kubectl run hello-minikube --image=
>>>>> gcr.io/google_containers/echoserver:1.4 --hostport=8000 --port=8080`
>>>>> as listed in the example. However, when I do `kubectl get pod` I get the
>>>>> status of the container as `pending`.
>>>>>
>>>>> It seems to me that the images are not being pulled from
>>>>> https://gcr.io/google_containers/. I also tried docker search
>>>>> gcr.io/google-containers/echoserver:1.4 and I get the error :
>>>>>
>>>>> Error response from daemon: invalid registry endpoint
>>>>> https://gcr.io/v0/: unable to ping registry endpoint
>>>>> https://gcr.io/v0/
>>>>> v2 ping attempt failed with error: Get https://gcr.io/v2/: dial tcp
>>>>> 64.233.184.82:443: i/o timeout
>>>>> v1 ping attempt failed with error: Get https://gcr.io/v1/_ping: dial
>>>>> tcp 64.233.184.82:443: i/o timeout. If this private registry supports
>>>>> only HTTP or HTTPS with an unknown CA certificate, please add
>>>>> `--insecure-registry gcr.io` to the daemon's arguments. In the case
>>>>> of HTTPS, if you have access to the registry's CA certificate, no need
>>>>> for
>>>>> the flag; simply place the CA certificate at /etc/docker/certs.d/
>>>>> gcr.io/ca.crt
>>>>>
>>>>> Does anyone know how to fix this problem? Thank you in advance.
>>>>>
>>>>>
--
You received this message because you are subscribed to the Google Groups
"Containers at Google" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-containers.
For more options, visit https://groups.google.com/d/optout.
