Bug#1036773: [EXTERNAL] Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails
+1
I my case installation of the NFS client fails (I'm behind a proxy) but the machine
boots fine.
$ cat Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "debian/testing64"
end
Last bit of the output from `vagrant up`
==> default: Machine booted and ready!
==> default: Installing NFS client...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get -yqq update
apt-get -yqq install nfs-common portmap
exit $?
Stdout from the command:
Stderr from the command:
W: Failed to fetch https://deb.debian.org/debian/dists/testing/InRelease Cannot initiate the connection to debian.map.fastly.net:443 (2a04:4e42:48::644). - connect (101: Network is unreachable) Could not connect to debian.map.fastly.net:443 (151.101.230.132), connection timed out Cannot initiate the connection to deb.debian.org:443 (2a04:4e42:36::644). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Package 'nfs-common' has no installation candidate
E: Unable to locate package portmap
Hope this helps,
________________________________________
From: Joshua Kugler <joshua@azariah.com>
Sent: 26 May 2023 04:37
To: Debian Bug Tracking System
Subject: [EXTERNAL] Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails
Package: cloud.debian.org
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I tried to use the debian/testing64 vagrant box.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I ran `vagrant up`. It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there
* What was the outcome of this action?
It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there for a while, it fails with:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=4 192.168.121.1:/home/jkugler/vmware/vagrant_debian /vagrant
Stdout from the command:
Stderr from the command:
mount.nfs: Connection refused
* What outcome did you expect instead?
I expected the machine to come up without issue.
I noticed in the default Vagrantfile that comes with the box, there is an NFS shared folder.
That should probably be removed and allow the user to configure shared folders as they see fit.
Reply to: