Have you checked these docs?
I think I also had to manually grant Full Disk Access privileges to /sbin/nfsd :
Hey @conrad – did you resolve your Installing NFS client... error?
This is the log I am getting with regards to the failed step (I can ping us.ports.ubuntu.com just fine):
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 http://us.ports.ubuntu.com/ubuntu-ports/dists/focal/InRelease Temporary failure resolving 'us.ports.ubuntu.com'
W: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/dists/focal-updates/InRelease Temporary failure resolving 'us.ports.ubuntu.com'
W: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/dists/focal-backports/InRelease Temporary failure resolving 'us.ports.ubuntu.com'
W: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/dists/focal-security/InRelease Temporary failure resolving 'us.ports.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/libt/libtirpc/libtirpc-common_1.2.5-1_all.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/libt/libtirpc/libtirpc3_1.2.5-1_arm64.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/r/rpcbind/rpcbind_1.2.5-8_arm64.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/k/keyutils/keyutils_1.6-6ubuntu1_arm64.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/libn/libnfsidmap/libnfsidmap2_0.25-5.1ubuntu1_arm64.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Failed to fetch http://us.ports.ubuntu.com/ubuntu-ports/pool/main/n/nfs-utils/nfs-common_1.3.4-2.5ubuntu3.4_arm64.deb Temporary failure resolving 'us.ports.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Hi @evance! Unfortunately I was unable to resolve the issue. I ended up having to dig out an intel mac and just fire up everything on that box. From what I recall with where I was with troubleshooting, it has to do with the way landrush seems to alter the DNS resolver of the Vagrant box. While the pings work, the actual way it grabs those packages seems to not be able to resolve. Since the DNS resolve conf is dynamically set, there wasn’t an easy way that I found to be able to work around it. I didn’t go down the path to try and fix it due to time constraints on the project, but I where I was going to start digging next was on hosts and iptables just to see if there was something there I missed. Our conclusion is that multisite with Roots is currently bricked for M1 architecture and that an alternative to landrush needs to be found or created to utilize it properly. Unfortunately, my team and I are not Python devs and wouldn’t know where to start.
1 Like
This landrush-ip pr just got merged and vagrant plugin install landrush will now install the new landrush-ip-0.2.7 gem with Arm64 support 
4 Likes
For anyone who comes here in the future, with multisite issues on an m1 mac, see: No DNS Resolution in development vm (vagrant, parallels, multisite, landrush) - #15 by craigpearson
1 Like