启动minishift或占用大量内存时，启动OpenShift群集永远不会结束

时间：2018-06-25 13:24:42

标签： out-of-memory minishift

每当我运行命令以将Virtualbox驱动程序启动Minishift到OS主机时，这都花了很长时间，而且永无止境。有时，我什至会收到一条有关达到存储限制的错误消息。

我想知道here

是否是持久性存储卷配置和使用错误。 
mike@mike-thinks:~$ minishift start --vm-driver=virtualbox
-- Starting profile 'minishift'
-- Check if depereccated options are used ... OK
-- Checking if https://github.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
-- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
-- Starting Minishift VM ........................ OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ... 
   Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ... 
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 8% used OK
-- OpenShift cluster will be configured with ...
   Version: v3.9.0
-- Copying oc binary from the OpenShift container image to VM .... OK
-- Starting OpenShift cluster ..............................................

我能做什么？我正在关注this tutorial，我只想进入允许我将oc添加到PATH的阶段

更新：openshift集群启动期间出现新错误

-- Starting OpenShift cluster ...........Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --use-existing-config --host-volumes-dir /var/lib/minishift/openshift.local.volumes --host-pv-dir /var/lib/minishift/openshift.local.pv --host-config-dir /var/lib/minishift/openshift.local.config --host-data-dir /var/lib/minishift/hostdata --public-hostname 192.168.99.100 --routing-suffix 192.168.99.100.nip.io
err     : exit status 1
output  : Deleted existing OpenShift container
Using nsenter mounter for OpenShift volumes
Using public hostname IP 192.168.99.100 as the host IP
Using 192.168.99.100 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
-- Starting OpenShift container ... 
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
FAIL
   Error: cannot access master readiness URL https://192.168.99.100:8443/healthz/ready
   Details:
     Last 10 lines of "origin" container log:
     E0625 14:47:40.905680    2341 proxier.go:252] Error removing userspace rule: error checking rule: fork/exec /usr/sbin/iptables: exec format error: 
     E0625 14:47:40.908353    2341 proxier.go:259] Error removing userspace rule: error checking rule: fork/exec /usr/sbin/iptables: exec format error: 
     E0625 14:47:40.910681    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-PORTALS-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 
     E0625 14:47:40.913452    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-PORTALS-HOST": fork/exec /usr/sbin/iptables: exec format error: 
     E0625 14:47:40.919209    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-HOST": fork/exec /usr/sbin/iptables: exec format error: 
     W0625 14:47:40.931698    2341 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
     E0625 14:47:40.932412    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 
     E0625 14:47:40.938345    2341 proxier.go:274] Error flushing userspace chain: error flushing chain "KUBE-NODEPORT-NON-LOCAL": fork/exec /usr/sbin/iptables: exec format error: 
     W0625 14:47:40.941639    2341 iptables.go:151] Error checking iptables version, assuming version at least 1.4.11: fork/exec /usr/sbin/iptables: exec format error
     F0625 14:47:40.949329    2341 network.go:177] error: Could not initialize Kubernetes Proxy. You must run this process as root (and if containerized, in the host network namespace as privileged) to use the service proxy: failed to initialize iptables: error creating chain "KUBE-PORTALS-CONTAINER": fork/exec /usr/sbin/iptables: exec format error: 


   Caused By:
     Error: Get https://192.168.99.100:8443/healthz/ready: dial tcp 192.168.99.100:8443: getsockopt: connection refused

3 个答案:

答案 0 :(得分：0)

如果这无论如何应该有所帮助，那么第一次对我来说也没有完成。但是，该图像在VirtualBox中处于“运行”状态。

我第二次通过提升的命令提示符运行它-并成功完成。但是也许在高级用户内部运行并没有帮助，但这是我第二次运行的事实。

答案 1 :(得分：0)

如果问题是您卡在Starting Minishift VM上（而不是OP），则问题可能是您在VPN上。尝试断开VPN连接，看看是否能解决您的问题。

答案 2 :(得分：-1)

有同样的问题。我在第一次启动（失败）时注意到一些网络流量，但网络连接速度较慢。我等了一段时间，直到网络流量很低，然后再试一次，然后开始工作。因此，可能在启动期间完成了一些Docker映像下载。

相关问题
最新问题