2017-04-10 137 views
0

我在遠程裸機實例上跟隨this fission tutorial。當我運行curl $ FISSION_URL(http://192.168.42.152:31313)它不會返回。我跑了以下命令:無法與來自主機的minikube羣集建立連接

  1. sudo lsof -i | grep 192.168.42.152。

ntpd 2860 ntp 32u IPv4 55241 0t0 UDP 192.168.42.1:ntp

dnsmasq 3392 libvirt-dnsmasq 5u IPv4 33870 0t0 UDP 192.168.42.1:domain

dnsmasq 3392 libvirt-dnsmasq 6u IPv4 33871 0t0 TCP 192.168.42.1:domain (LISTEN)

  • 捲曲-vvv $ FISSION_URL。
  • Rebuilt URL to: http://192.168.42.152:31313/

    Trying 192.168.42.152...

    Connected to 192.168.42.152 (192.168.42.152) port 31313 (#0)

    GET/HTTP/1.1

    Host: 192.168.42.152:31313

    User-Agent: curl/7.47.0

    Accept: /

  • 須藤的iptables -L

    Chain INPUT (policy ACCEPT) 
    target  prot opt source    destination   
    ACCEPT  udp -- anywhere    anywhere    udp dpt:domain 
    ACCEPT  tcp -- anywhere    anywhere    tcp dpt:domain 
    ACCEPT  udp -- anywhere    anywhere    udp dpt:bootps 
    ACCEPT  tcp -- anywhere    anywhere    tcp dpt:bootps 
    ACCEPT  udp -- anywhere    anywhere    udp dpt:domain 
    ACCEPT  tcp -- anywhere    anywhere    tcp dpt:domain 
    ACCEPT  udp -- anywhere    anywhere    udp dpt:bootps 
    ACCEPT  tcp -- anywhere    anywhere    tcp dpt:bootps 
    Chain FORWARD (policy ACCEPT) 
    target  prot opt source    destination   
    DOCKER-ISOLATION all -- anywhere    anywhere    
    DOCKER  all -- anywhere    anywhere    
    ACCEPT  all -- anywhere    anywhere    ctstate RELATED,ESTABLISHED 
    ACCEPT  all -- anywhere    anywhere    
    ACCEPT  all -- anywhere    anywhere    
    ACCEPT  all -- anywhere    192.168.122.0/24  ctstate RELATED,ESTABLISHED 
    ACCEPT  all -- 192.168.122.0/24  anywhere    
    ACCEPT  all -- anywhere    anywhere    
    REJECT  all -- anywhere    anywhere    reject-with icmp-port-unreachable 
    REJECT  all -- anywhere    anywhere    reject-with icmp-port-unreachable 
    ACCEPT  all -- anywhere    anywhere    
    REJECT  all -- anywhere    anywhere    reject-with icmp-port-unreachable 
    REJECT  all -- anywhere    anywhere    reject-with icmp-port-unreachable 
    Chain OUTPUT (policy ACCEPT) 
    target  prot opt source    destination   
    ACCEPT  udp -- anywhere    anywhere    udp dpt:bootpc 
    ACCEPT  udp -- anywhere    anywhere    udp dpt:bootpc 
    Chain DOCKER (1 references) 
    target  prot opt source    destination   
    Chain DOCKER-ISOLATION (1 references) 
    target  prot opt source    destination     
    
    RETURN  all -- anywhere    anywhere  
    
  • 我在我應該如何與調試此繼續進行不確定。我相信主機能夠與guest(minikube IP)連接,但無法檢索數據。任何人都可以指導我如何解決這個問題?

    回答

    1

    一旦你開始了minikube實例並運行在doc給出的命令,說

    kubectl create -f http://fission.io/fission.yaml 
    kubectl create -f http://fission.io/fission-nodeport.yaml 
    

    然後運行下面的設置kubernetes背景

    kubectl config set-context minikube --namespace fission 
    

    我們得到當前部署的狀態請運行,請輸出以下命令:

    kubectl get pods -o wide 
    kubectl get svc -o wide 
    kubectl get events 
    

    對我來說這是工作:

    $ export FISSION_URL=http://$(minikube ip):31313 
    $ curl $FISSION_URL 
    {"message": "Fission API", "version": "0.1.0"} 
    

    我的狀態如下:

    $ kubectl get pods -o wide 
    NAME       READY  STATUS RESTARTS AGE  IP   NODE 
    controller-1637203237-g5lw1 1/1  Running 0   16m  172.17.0.6 minikube 
    etcd-2122244727-6vl4v   1/1  Running 0   16m  172.17.0.8 minikube 
    kubewatcher-2300228496-7kbw3 1/1  Running 1   16m  172.17.0.7 minikube 
    poolmgr-3531518326-nsxmr  1/1  Running 3   16m  172.17.0.5 minikube 
    router-2621354073-q1hw7  1/1  Running 3   16m  172.17.0.4 minikube 
    

    $ kubectl get svc -o wide 
    NAME   CLUSTER-IP EXTERNAL-IP PORT(S)  AGE  SELECTOR 
    controller 10.0.0.191 <nodes>  80:31313/TCP 15m  svc=controller 
    etcd   10.0.0.41 <none>  2379/TCP  16m  svc=etcd 
    poolmgr  10.0.0.252 <none>  80/TCP   16m  svc=poolmgr 
    router  10.0.0.108 <nodes>  80:31314/TCP 15m  svc=router 
    

    和事件here

    +0

    感謝您的回覆。當我運行'kubectl獲取豆莢寬'我看到我所有的豆莢都在'ContainerCreating'狀態。我檢查了'kubectl get events',發現這個錯誤:'Warning \t FailedSync \t同步窗格時出錯,跳過:ImagePullBackOff:「Back-off pulling image \」無法爲「POD」啓動「StartContainer」gcr.io/google_containers/pause -amd64:3.0 \「」。我發現[this](https://github.com/kubernetes/minikube/issues/322)有類似的問題。你能指導我在哪裏可以爲代理設置'--docker-env標誌'嗎?我無法理解修復。 謝謝! –

    +0

    你可以在這個[issue]中找到代理的幫助(https://github.com/kubernetes/minikube/issues/530#issuecomment-250801735) – surajd

    +0

    謝謝!但是當我運行env | grep -i代理它不會返回任何東西。所以我不認爲代理是這個原因。 我注意到,當我運行kubectl獲取端點時,它顯示我沒有IP被分配給任何一個pod。這是正常的嗎?我無法找到關於此在線的任何內容。 –

    相關問題