为什么gta5一直errorhot syncingg podcloud saves

Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.
Kubernetes官网地址
但是,进入首页后依然会很懵逼,进入Documentation页面会更懵逼,对于初学者想依照文档搭建个环境try一下相当费劲,太乱了,下面我会整理下相关步骤以及文档地址。
kubernetes运行环境选择
官方说明:
Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to rack of bare metal servers. The effort required to set up a cluster varies from running a single command to crafting your own customized cluster. Use this guide to choose a solution that fits your needs.
Local-machine Solutions
just want to “kick the tires” on Kubernetes
Hosted Solutions
ready to scale up to more machines and higher availability
Turnkey Cloud Solutions
you already have a way to configure hosting resources
Custom Solutions
这里我们选择最简单的Local-machine Solutions模式。
我是Mac环境,会以mac为主,单操作步骤也会说明其他环境如何安装。
在minikube上运行Local-machine Solutions模式
官网说明:
官方说明会要求你先安装minikube,安装minikube说明在
,这里会要求先安装Hypervisor
安装Hypervisor
我选择的是OS X的第二个选项,VirtualBox,因为这个下载下来直接就是一个dmg文件,方便安装 VirtualBox-5.1.26-117224-OSX.dmg,94M。
安装后启动
红框内是因为我启动过本地的minikube,刚安装好时是没有的。
安装kubectl
官方说明:
根据环境选择不同页签哦。
我选择macos命令行输入 curl -LO
下载完成后,执行chmod +x ./kubectl,保证其执行权限
将包移动至类路径下
sudo mv ./kubectl /usr/local/bin/kubectl
到此,kubectl就安装完成了,这页官网剩下的内容可以忽略或简单看下即可了。
安装Minikube
现在才开始真正安装Minikube
Windows安装包在这一页也是可以找到的,往下翻即可。
curl -Lo minikube
&& chmod +x minikube && sudo mv minikube /usr/local/bin/
好了,minikube安装好了,需要的安装包基本都已ok啦。
现在可以开始配置了。
依次执行如下5个步骤
bjjbgi-3-86:~ zhangxiaolong$ minikube start
Starting local Kubernetes v1.7.0 cluster...
Starting VM...
Downloading Minikube ISO
97.80 MB / 97.80 MB [==============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Starting cluster components...
Connecting to cluster...
Setting up kubeconfig...
Kubectl is now configured to use the cluster.
bjjbgi-3-86:~ zhangxiaolong$ kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8082 deployment "hello-minikube" created
deployment "hello-minikube" created
bjjbgi-3-86:~ zhangxiaolong$ kubectl expose deployment hello-minikube --type=NodePort
service "hello-minikube" exposed
bjjbgi-3-86:~ zhangxiaolong$ kubectl get pod
hello-minikube--5rr1t
ContainerCreating
bjjbgi-3-86:~ zhangxiaolong$ curl $(minikub service hello-minikube --url)
-bash: minikub: command not found
curl: try 'curl --help' or 'curl --manual' for more information
bjjbgi-3-86:~ zhangxiaolong$ curl $(minikube service hello-minikube --url)
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
我的在第5步的时候,报了Waiting, endpoint for service is not ready yet.
试了几次都不行,官网上第5步成功如下图
到此,我的最后一步测试没通过,明天再看吧,你们可以试试。
时间转到日。
折腾了一天,算是有了点小进展,补充在这里。
昨天安装完minikube后就通过 curl $(minikube service hello-minikube –url)来测试发现 一直在waiting,其实这个hello-minikube根本没有起来。
可以通过命令kubectl get pod查看
bjjbgi-3-86:~ zhangxiaolong$ kubectl get pod
hello-minikube--5rr1t
ContainerCreating
可以看到这个服务的status是ContainerCreating,这个代表什么含义呢,表面意思是容器创建中,
我们可以通过kubectl describe pod命令查看详细信息
bjjbgi-3-86:~ zhangxiaolong$ kubectl describe pod
hello-minikube--5rr1t
Namespace:
minikube/192.168.99.100
Start Time: Tue, 01 Aug 2017 18:53:27 +0800
pod-template-hash=
run=hello-minikube
Annotations:
kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"default","name":"hello-minikube-","uid":"a5e87f14-76a7-11e7-a070-080027...
172.17.0.3
Created By: ReplicaSet/hello-minikube-
Controlled By:
ReplicaSet/hello-minikube-
Containers:
hello-minikube:
Container ID:
gcr.io/google_containers/echoserver:1.4
deployment
hello-minikube
ErrImagePull
Restart Count:
Environment:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-xxfxr (ro)
Conditions:
Initialized
PodScheduled
default-token-xxfxr:
Secret (a volume populated by a Secret)
SecretName: default-token-xxfxr
QoS Class:
BestEffort
Node-Selectors: &none&
Tolerations:
FirstSeen LastSeen
SubObjectPath
--------- --------
-------------
kubelet, minikube
SuccessfulMountVolume
MountVolume.SetUp succeeded for volume "default-token-xxfxr"
kubelet, minikube
spec.containers{hello-minikube} Warning
Failed to pull image "gcr.io/google_containers/echoserver:1.4": rpc error: code = 2 desc = Error response from daemon: {"message":"Get https:
kubelet, minikube
spec.containers{hello-minikube} Warning
Failed to pull image "gcr.io/google_containers/echoserver:1.4": rpc error: code = 2 desc = Error response from daemon: {"message":"Get https://gcr.io/v1/_ping: dial tcp 64.233.187.82:443: i/o timeout"}
kubelet, minikube
spec.containers{hello-minikube} Warning
Failed to pull image "gcr.io/google_containers/echoserver:1.4": rpc error: code = 2 desc = Error response from daemon: {"message":"Get https://gcr.io/v2/google_containers/echoserver/manifests/1.4: Get https://gcr.io/v2/token?scope=repository%3Agoogle_containers%2Fechoserver%3Apull\u0026service=gcr.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
kubelet, minikube
spec.containers{hello-minikube} Warning
Failed to pull image "gcr.io/google_containers/echoserver:1.4": rpc error: code = 2 desc = Error response from daemon: {"message":"Get https://gcr.io/v1/_ping: dial tcp 74.125.203.82:443: i/o timeout"}
kubelet, minikube
spec.containers{hello-minikube} Normal
Back-off pulling image "gcr.io/google_containers/echoserver:1.4"
kubelet, minikube
FailedSync
Error syncing pod
kubelet, minikube
spec.containers{hello-minikube} Normal
pulling image "gcr.io/google_containers/echoserver:1.4"
kubelet, minikube
SuccessfulMountVolume
MountVolume.SetUp succeeded for volume "default-token-xxfxr"
kubelet, minikube
spec.containers{hello-minikube} Normal
pulling image "gcr.io/google_containers/echoserver:1.4"
kubelet, minikube
spec.containers{hello-minikube} Warning
Failed to pull image "gcr.io/google_containers/echoserver:1.4": rpc error: code = 2 desc = Error response from daemon: {"message":"Get https://gcr.io/v1/_ping: dial tcp 64.233.189.82:443: i/o timeout"}
kubelet, minikube
FailedSync
Error syncing pod
kubelet, minikube
spec.containers{hello-minikube} Normal
Back-off pulling image "gcr.io/google_containers/echoserver:1.4"
相信你看到了Failed
Failed to pull image “gcr.io/google_containers/echoserver:1.4”这行信息。
网上搜了一圈的资料,是因为gcr.io这个外国网站,我们访问不到。
所以出现了一些方案
1 用VPN,翻墙出去
2 使用国内镜像,推荐使用阿里云的
minikube start kubectl run hello-minikube --image=registry.cn-hangzhou.aliyuncs.com/google-container/echoserver:1.4 --port=8080 kubectl expose deployment hello-minikube --type=NodePort kubectl get pod
作者:scipio
链接:http:
來源:简书
著作权归作者所有。商业转载请联系作者获得授权,非商业转载请注明出处。
3 搭建自己的docker镜像仓库,将echoserver从国内镜像中pull下来,然后推送到自己的仓库上去,然后
minikube start kubectl run hello-minikube

我要回帖

更多关于 cloud pod 的文章

 

随机推荐