search

pires / kubernetes-vagrant-coreos-cluster

Kubernetes cluster (for testing purposes) made easy with Vagrant and CoreOS.
Apache License 2.0
597 stars 205 forks source link

Error - mount.nfs: Connection timed out #310

Open amitoj opened 6 years ago

amitoj commented 6 years ago

Hi,

Any solution for this?

[root@xyz kubernetes-vagrant-coreos-cluster]# NODE_MEM=2048 NODE_CPUS=1 NODES=3 USE_KUBE_UI=true KUBERNETES_VERSION=1.10.4 vagrant up WARNING: Vagrant has detected the vagrant-triggers plugin. This plugin conflicts with the internal triggers implementation. Please uninstall the vagrant-triggers plugin and run the command again if you wish to use the core trigger feature. To uninstall the plugin, run the command shown below:

vagrant plugin uninstall vagrant-triggers

Note that the community plugin vagrant-triggers and the core trigger feature in Vagrant do not have compatible syntax.

To disable this warning, set the environment variable VAGRANT_USE_VAGRANT_TRIGGERS. Bringing machine 'master' up with 'virtualbox' provider... Bringing machine 'node-01' up with 'virtualbox' provider... Bringing machine 'node-02' up with 'virtualbox' provider... Bringing machine 'node-03' up with 'virtualbox' provider... ==> master: Running triggers before up... ==> master: 2018-06-20 19:58:22 +0100: setting up Kubernetes master... ==> master: Setting Kubernetes version 1.10.4 ==> master: Importing base box 'coreos-alpha'... ==> master: Matching MAC address for NAT networking... ==> master: Checking if box 'coreos-alpha' is up to date... ==> master: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_master_1529521109268_66424 ==> master: Clearing any previously set network interfaces... ==> master: Preparing network interfaces based on configuration... master: Adapter 1: nat master: Adapter 2: hostonly ==> master: Forwarding ports... master: 22 (guest) => 2222 (host) (adapter 1) ==> master: Running 'pre-boot' VM customizations... ==> master: Booting VM... ==> master: Waiting for machine to boot. This may take a few minutes... master: SSH address: 127.0.0.1:2222 master: SSH username: core master: SSH auth method: private key master: Warning: Connection reset. Retrying... ==> master: Machine booted and ready! ==> master: Setting hostname... ==> master: Configuring and enabling network interfaces... ==> master: Exporting NFS shared folders... ==> master: Preparing to edit /etc/exports. Administrator privileges will be required... ==> master: Mounting NFS shared folders... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

mount -o vers=3,udp,nolock,vers=3,udp,noatime 172.17.8.1:/root/workspace/kubernetes-vagrant-coreos-cluster /vagrant

Stdout from the command:

Stderr from the command:

mount.nfs: Connection timed out

pires commented 6 years ago

Could your network have 172.17.8.1 assigned somewhere else?