New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFS access denied by server while mounting #100

Closed
tomlankhorst opened this Issue Aug 8, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@tomlankhorst
Contributor

tomlankhorst commented Aug 8, 2016

When using NFS as shared folder mechanism an error occurs while mounting:

sudo mount -o vers=3,udp 10.0.3.1:/home/tomlankhorst/Repos/my-repo /data/web

mount.nfs: access denied by server while mounting 10.0.3.1:/home/tomlankhorst/Repos/my-repo

Exports looks as follows:

"/home/tomlankhorst/Repos/my-repo" 10.0.0.0/16(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=2586260242)

Mounting locally does work when changing IP to 127.0.0.1.

Has it to do with a known issue of the Ubuntu 14.04 LXC base box?

We can't get the NFS client to be installed on the containers used for building Ubuntu 13.04 / 13.10 / 14.04 base boxes.

I don't think so as the NFS client is available.

@vdloo

This comment has been minimized.

Show comment
Hide comment
@vdloo

vdloo Aug 9, 2016

Member

Hi,

That's unfortunate. These NFS mount issues are difficult to debug. I just tested on my Ubuntu 14.04 machine and everything seems to be working fine with lxc:

$ vagrant up --provider=lxc
Bringing machine 'hypernode' up with 'lxc' provider...
==> hypernode: Will use PHP 7. If you want PHP 5.5 instead change the php version in local.yml.
==> hypernode: Importing base box 'hypernode_php7'...
==> hypernode: WARNING: You are using a base box that has a format that has been deprecated, please upgrade to a new one.
==> hypernode: Checking if box 'hypernode_php7' is up to date...
==> hypernode: Setting up mount entries for shared folders...
    hypernode: /vagrant => /home/vdloo/code/projects/hypernode-vagrant
==> hypernode: Starting container...
==> hypernode: Waiting for machine to boot. This may take a few minutes...
    hypernode: SSH address: 10.0.3.180:22
    hypernode: SSH username: vagrant
    hypernode: SSH auth method: private key
    hypernode: 
    hypernode: Vagrant insecure key detected. Vagrant will automatically replace
    hypernode: this with a newly generated keypair for better security.
    hypernode: 
    hypernode: Inserting generated public key within guest...
    hypernode: Removing insecure key from the guest if it's present...
    hypernode: Key inserted! Disconnecting and reconnecting using new SSH key...
==> hypernode: Machine booted and ready!
==> hypernode: Setting hostname...
==> hypernode: Installing NFS client...
==> hypernode: Exporting NFS shared folders...
==> hypernode: Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd running
==> hypernode: Mounting NFS shared folders...
==> hypernode: Updating /etc/hosts file on active guest machines...
==> hypernode: Updating /etc/hosts file on host machine (password may be required)...
==> hypernode: Running provisioner: shell...

My exports

$ cat /etc/exports 
# /etc/exports: the access control list for filesystems which may be exported
#       to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
# VAGRANT-BEGIN: 1000 hypernode-vagrant_hypernode_1470722578600_71301
"/home/vdloo/code/projects/hypernode-vagrant/data/web/magento2" 10.0.3.180(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3751958210)
"/home/vdloo/code/projects/hypernode-vagrant/data/web/nginx" 10.0.3.180(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3063646465)
# VAGRANT-END: 1000 hypernode-vagrant_hypernode_1470722578600_71301

Also on Virtualbox:

hypernode-vagrant$ vagrant up
Bringing machine 'hypernode' up with 'virtualbox' provider...
==> hypernode: Will use PHP 7. If you want PHP 5.5 instead change the php version in local.yml.
==> hypernode: Box 'hypernode_php7' could not be found. Attempting to find and install...
    hypernode: Box Provider: virtualbox
    hypernode: Box Version: >= 0
==> hypernode: Loading metadata for box 'http://vagrant.hypernode.com/customer/php7/catalog.json'
    hypernode: URL: http://vagrant.hypernode.com/customer/php7/catalog.json
==> hypernode: Adding box 'hypernode_php7' (v3177) for provider: virtualbox
    hypernode: Downloading: http://vagrant.hypernode.com/customer/php7/hypernode_php7.virtualbox.release-3177.box
    hypernode: Calculating and comparing box checksum...
==> hypernode: Successfully added box 'hypernode_php7' (v3177) for 'virtualbox'!
==> hypernode: Importing base box 'hypernode_php7'...
==> hypernode: Matching MAC address for NAT networking...
==> hypernode: Checking if box 'hypernode_php7' is up to date...
==> hypernode: Setting the name of the VM: hypernode-vagrant_hypernode_1470721764098_60026
==> hypernode: Clearing any previously set network interfaces...
==> hypernode: Preparing network interfaces based on configuration...
    hypernode: Adapter 1: nat
    hypernode: Adapter 2: hostonly
==> hypernode: Forwarding ports...
    hypernode: 80 (guest) => 8080 (host) (adapter 1)
    hypernode: 3306 (guest) => 3307 (host) (adapter 1)
    hypernode: 22 (guest) => 2222 (host) (adapter 1)
==> hypernode: Running 'pre-boot' VM customizations...
==> hypernode: vagrant.actions.vm.boot.booting
==> hypernode: Waiting for machine to boot. This may take a few minutes...
    hypernode: SSH address: 127.0.0.1:2222
...
==> hypernode: Machine booted and ready!
[hypernode] GuestAdditions versions on your host (5.0.8) and guest (5.0.26) do not match.
...
==> hypernode: Setting hostname...
==> hypernode: Configuring and enabling network interfaces...
==> hypernode: Exporting NFS shared folders...
==> hypernode: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for vdloo: 
nfsd not running
 * Exporting directories for NFS kernel daemon...                                                                                                                                                                                       [ OK ] 
 * Starting NFS kernel daemon                                                                                                                                                                                                           [ OK ] 
==> hypernode: Mounting NFS shared folders...
==> hypernode: Mounting shared folders...
    hypernode: /vagrant => /home/vdloo/code/projects/hypernode-vagrant
==> hypernode: Updating /etc/hosts file on active guest machines...
==> hypernode: Updating /etc/hosts file on host machine (password may be required)...
==> hypernode: Running provisioner: shell...

For virtualbox my /etc/exports look like:

# VAGRANT-BEGIN: 1000 f45dc662-26d6-4fbc-9cb6-7b3c09631d07
"/home/vdloo/code/projects/hypernode-vagrant/data/web/magento2" 172.28.128.3(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3751958210)
"/home/vdloo/code/projects/hypernode-vagrant/data/web/nginx" 172.28.128.3(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3063646465)
# VAGRANT-END: 1000 f45dc662-26d6-4fbc-9cb6-7b3c09631d07

I did notice however that nfs_guest does not work with lxc so you can't use that as an alternative. It is generally more compatible because most of the configuration happens inside the machine, not on the host. The vagrant-nfs_guest plugin will yield this error:

Missing provider support in vagrant-nfs_guest plugin for retrieving host and guest IPs.

Currently only Virtualbox provider is supported.

Have you seen my comments in this thread? Maybe those can point you in the right direction. Also, do you have an encrypted homedir by any chance? That can cause permissions issues, but seems unlikely if using 127.0.0.1 does work.

If you figured it out I'd love to know what the problem was for future reference.

Member

vdloo commented Aug 9, 2016

Hi,

That's unfortunate. These NFS mount issues are difficult to debug. I just tested on my Ubuntu 14.04 machine and everything seems to be working fine with lxc:

$ vagrant up --provider=lxc
Bringing machine 'hypernode' up with 'lxc' provider...
==> hypernode: Will use PHP 7. If you want PHP 5.5 instead change the php version in local.yml.
==> hypernode: Importing base box 'hypernode_php7'...
==> hypernode: WARNING: You are using a base box that has a format that has been deprecated, please upgrade to a new one.
==> hypernode: Checking if box 'hypernode_php7' is up to date...
==> hypernode: Setting up mount entries for shared folders...
    hypernode: /vagrant => /home/vdloo/code/projects/hypernode-vagrant
==> hypernode: Starting container...
==> hypernode: Waiting for machine to boot. This may take a few minutes...
    hypernode: SSH address: 10.0.3.180:22
    hypernode: SSH username: vagrant
    hypernode: SSH auth method: private key
    hypernode: 
    hypernode: Vagrant insecure key detected. Vagrant will automatically replace
    hypernode: this with a newly generated keypair for better security.
    hypernode: 
    hypernode: Inserting generated public key within guest...
    hypernode: Removing insecure key from the guest if it's present...
    hypernode: Key inserted! Disconnecting and reconnecting using new SSH key...
==> hypernode: Machine booted and ready!
==> hypernode: Setting hostname...
==> hypernode: Installing NFS client...
==> hypernode: Exporting NFS shared folders...
==> hypernode: Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd running
==> hypernode: Mounting NFS shared folders...
==> hypernode: Updating /etc/hosts file on active guest machines...
==> hypernode: Updating /etc/hosts file on host machine (password may be required)...
==> hypernode: Running provisioner: shell...

My exports

$ cat /etc/exports 
# /etc/exports: the access control list for filesystems which may be exported
#       to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
# VAGRANT-BEGIN: 1000 hypernode-vagrant_hypernode_1470722578600_71301
"/home/vdloo/code/projects/hypernode-vagrant/data/web/magento2" 10.0.3.180(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3751958210)
"/home/vdloo/code/projects/hypernode-vagrant/data/web/nginx" 10.0.3.180(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3063646465)
# VAGRANT-END: 1000 hypernode-vagrant_hypernode_1470722578600_71301

Also on Virtualbox:

hypernode-vagrant$ vagrant up
Bringing machine 'hypernode' up with 'virtualbox' provider...
==> hypernode: Will use PHP 7. If you want PHP 5.5 instead change the php version in local.yml.
==> hypernode: Box 'hypernode_php7' could not be found. Attempting to find and install...
    hypernode: Box Provider: virtualbox
    hypernode: Box Version: >= 0
==> hypernode: Loading metadata for box 'http://vagrant.hypernode.com/customer/php7/catalog.json'
    hypernode: URL: http://vagrant.hypernode.com/customer/php7/catalog.json
==> hypernode: Adding box 'hypernode_php7' (v3177) for provider: virtualbox
    hypernode: Downloading: http://vagrant.hypernode.com/customer/php7/hypernode_php7.virtualbox.release-3177.box
    hypernode: Calculating and comparing box checksum...
==> hypernode: Successfully added box 'hypernode_php7' (v3177) for 'virtualbox'!
==> hypernode: Importing base box 'hypernode_php7'...
==> hypernode: Matching MAC address for NAT networking...
==> hypernode: Checking if box 'hypernode_php7' is up to date...
==> hypernode: Setting the name of the VM: hypernode-vagrant_hypernode_1470721764098_60026
==> hypernode: Clearing any previously set network interfaces...
==> hypernode: Preparing network interfaces based on configuration...
    hypernode: Adapter 1: nat
    hypernode: Adapter 2: hostonly
==> hypernode: Forwarding ports...
    hypernode: 80 (guest) => 8080 (host) (adapter 1)
    hypernode: 3306 (guest) => 3307 (host) (adapter 1)
    hypernode: 22 (guest) => 2222 (host) (adapter 1)
==> hypernode: Running 'pre-boot' VM customizations...
==> hypernode: vagrant.actions.vm.boot.booting
==> hypernode: Waiting for machine to boot. This may take a few minutes...
    hypernode: SSH address: 127.0.0.1:2222
...
==> hypernode: Machine booted and ready!
[hypernode] GuestAdditions versions on your host (5.0.8) and guest (5.0.26) do not match.
...
==> hypernode: Setting hostname...
==> hypernode: Configuring and enabling network interfaces...
==> hypernode: Exporting NFS shared folders...
==> hypernode: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for vdloo: 
nfsd not running
 * Exporting directories for NFS kernel daemon...                                                                                                                                                                                       [ OK ] 
 * Starting NFS kernel daemon                                                                                                                                                                                                           [ OK ] 
==> hypernode: Mounting NFS shared folders...
==> hypernode: Mounting shared folders...
    hypernode: /vagrant => /home/vdloo/code/projects/hypernode-vagrant
==> hypernode: Updating /etc/hosts file on active guest machines...
==> hypernode: Updating /etc/hosts file on host machine (password may be required)...
==> hypernode: Running provisioner: shell...

For virtualbox my /etc/exports look like:

# VAGRANT-BEGIN: 1000 f45dc662-26d6-4fbc-9cb6-7b3c09631d07
"/home/vdloo/code/projects/hypernode-vagrant/data/web/magento2" 172.28.128.3(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3751958210)
"/home/vdloo/code/projects/hypernode-vagrant/data/web/nginx" 172.28.128.3(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3063646465)
# VAGRANT-END: 1000 f45dc662-26d6-4fbc-9cb6-7b3c09631d07

I did notice however that nfs_guest does not work with lxc so you can't use that as an alternative. It is generally more compatible because most of the configuration happens inside the machine, not on the host. The vagrant-nfs_guest plugin will yield this error:

Missing provider support in vagrant-nfs_guest plugin for retrieving host and guest IPs.

Currently only Virtualbox provider is supported.

Have you seen my comments in this thread? Maybe those can point you in the right direction. Also, do you have an encrypted homedir by any chance? That can cause permissions issues, but seems unlikely if using 127.0.0.1 does work.

If you figured it out I'd love to know what the problem was for future reference.

@tomlankhorst

This comment has been minimized.

Show comment
Hide comment
@tomlankhorst

tomlankhorst Aug 9, 2016

Contributor

Hi Rick,

I've altered the sudoers file but this makes no effect. Indeed, I don't need to enter my password anymore but that wan't the issue so to see.

I think it is remarkable that my export files look the same:

On my host:

# VAGRANT-BEGIN: 1000 myshop_hypernode_1470727368375_18737
"/home/tomlankhorst/Repos/myshop" 10.0.3.178(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=2586260242)
# VAGRANT-END: 1000 myshop_hypernode_1470727368375_18737

Firewall is disabled:

vagrant@7daa75-myshop-magweb-vgr:~$ sudo ufw status
Status: inactive

Host -> Client pingable and v.v.

NFS export even shows up on the client. Showing all NFS exports of the host on the client:

vagrant@7daa75-myshop-magweb-vgr:~$ showmount -e 10.0.3.1
/home/tomlankhorst/Repos/myshop 10.0.3.178
Contributor

tomlankhorst commented Aug 9, 2016

Hi Rick,

I've altered the sudoers file but this makes no effect. Indeed, I don't need to enter my password anymore but that wan't the issue so to see.

I think it is remarkable that my export files look the same:

On my host:

# VAGRANT-BEGIN: 1000 myshop_hypernode_1470727368375_18737
"/home/tomlankhorst/Repos/myshop" 10.0.3.178(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=2586260242)
# VAGRANT-END: 1000 myshop_hypernode_1470727368375_18737

Firewall is disabled:

vagrant@7daa75-myshop-magweb-vgr:~$ sudo ufw status
Status: inactive

Host -> Client pingable and v.v.

NFS export even shows up on the client. Showing all NFS exports of the host on the client:

vagrant@7daa75-myshop-magweb-vgr:~$ showmount -e 10.0.3.1
/home/tomlankhorst/Repos/myshop 10.0.3.178
@tomlankhorst

This comment has been minimized.

Show comment
Hide comment
@tomlankhorst

tomlankhorst Aug 9, 2016

Contributor

Enabling RPC debugging on the server:

% sudo rpcdebug -m nfsd -s all

Verbose mounting of NFS share on client:

vagrant@7daa75-myshop-magweb-vgr:~$ sudo mount -o vers=3,udp 10.0.3.1:/home/tomlankhorst/Repos/myshop /data/web/ -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Aug  9 07:44:09 2016
mount.nfs: trying text-based options 'vers=3,udp,addr=10.0.3.1'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 10.0.3.1 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.0.3.1 prog 100005 vers 3 prot UDP port 39047
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 10.0.3.1:/home/tomlankhorst/Repos/myshop

Tail of the syslog on host:

% tail /var/log/syslog
Aug  9 09:40:43 build kernel: [110652.649313] nfsd_dispatch: vers 3 proc 0
Aug  9 09:40:43 build kernel: [110652.650493] audit: type=1400 audit(1470728443.604:129): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/data/web/" pid=15496 comm="mount.nfs" fstype="nfs" srcname="10.0.3.1:/home/tomlankhorst/Repos/myshop"

AppArmor problems... Seems that NFS is not allowed by default for LXC containers. Must be noted though that the AppArmor service is not actively running on the system but it is installed though (came with LXC probabily).

So, I went looking for the LXC config and the corresponding AppArmor profile that was set. I changed to policy to unconfined:

vim ~/.vagrant.d/boxes/hypernode_php5/3172/lxc/lxc.conf

# When using LXC with apparmor, uncomment the next line to run unconfined:
lxc.aa_profile = unconfined 

Deleted the Vagrant box, restart and now it's working... Check that Vagrant destroy actually destroys the LXC machine: sudo lxc ls, sudo lxc-destroy --name machine...

Thanks for the help anyhow!

Contributor

tomlankhorst commented Aug 9, 2016

Enabling RPC debugging on the server:

% sudo rpcdebug -m nfsd -s all

Verbose mounting of NFS share on client:

vagrant@7daa75-myshop-magweb-vgr:~$ sudo mount -o vers=3,udp 10.0.3.1:/home/tomlankhorst/Repos/myshop /data/web/ -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Aug  9 07:44:09 2016
mount.nfs: trying text-based options 'vers=3,udp,addr=10.0.3.1'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 10.0.3.1 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.0.3.1 prog 100005 vers 3 prot UDP port 39047
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 10.0.3.1:/home/tomlankhorst/Repos/myshop

Tail of the syslog on host:

% tail /var/log/syslog
Aug  9 09:40:43 build kernel: [110652.649313] nfsd_dispatch: vers 3 proc 0
Aug  9 09:40:43 build kernel: [110652.650493] audit: type=1400 audit(1470728443.604:129): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/data/web/" pid=15496 comm="mount.nfs" fstype="nfs" srcname="10.0.3.1:/home/tomlankhorst/Repos/myshop"

AppArmor problems... Seems that NFS is not allowed by default for LXC containers. Must be noted though that the AppArmor service is not actively running on the system but it is installed though (came with LXC probabily).

So, I went looking for the LXC config and the corresponding AppArmor profile that was set. I changed to policy to unconfined:

vim ~/.vagrant.d/boxes/hypernode_php5/3172/lxc/lxc.conf

# When using LXC with apparmor, uncomment the next line to run unconfined:
lxc.aa_profile = unconfined 

Deleted the Vagrant box, restart and now it's working... Check that Vagrant destroy actually destroys the LXC machine: sudo lxc ls, sudo lxc-destroy --name machine...

Thanks for the help anyhow!

@vdloo

This comment has been minimized.

Show comment
Hide comment
@vdloo

vdloo Aug 9, 2016

Member

Thanks for investigating! Ran into the same issue trying to get vagrant-nfs_guest to work with lxc.

By the way, we noticed something similar for our own internal Vagrant images a while back transitioning to Ubuntu 16.04 hosts. For future googlers, if this didn't solve it and you're having app armor related issues with lxc try this:

LXC_VERSION = `lxc-ls --version`.strip unless defined? LXC_VERSION
config.vm.provider :lxc do |lxc, override|
  if LXC_VERSION >= "1.1.0"
    # required on 16.04 in combination with apparmor
    # https://github.com/fgrehm/vagrant-lxc/issues/333
    # Allow start without AppArmor, otherwise Box will not Start on Ubuntu 14.10
    # see https://github.com/fgrehm/vagrant-lxc/issues/333
    lxc.customize 'aa_allow_incomplete', 1
  end
Member

vdloo commented Aug 9, 2016

Thanks for investigating! Ran into the same issue trying to get vagrant-nfs_guest to work with lxc.

By the way, we noticed something similar for our own internal Vagrant images a while back transitioning to Ubuntu 16.04 hosts. For future googlers, if this didn't solve it and you're having app armor related issues with lxc try this:

LXC_VERSION = `lxc-ls --version`.strip unless defined? LXC_VERSION
config.vm.provider :lxc do |lxc, override|
  if LXC_VERSION >= "1.1.0"
    # required on 16.04 in combination with apparmor
    # https://github.com/fgrehm/vagrant-lxc/issues/333
    # Allow start without AppArmor, otherwise Box will not Start on Ubuntu 14.10
    # see https://github.com/fgrehm/vagrant-lxc/issues/333
    lxc.customize 'aa_allow_incomplete', 1
  end

vdloo added a commit that referenced this issue Aug 9, 2016

@vdloo

This comment has been minimized.

Show comment
Hide comment
@vdloo

vdloo Aug 9, 2016

Member

The lxc.aa_profile == unconfined setting is now baked into the image (>= release-3180)

$ grep aa_profile ~/.vagrant.d/boxes/hypernode_php7/3180/lxc/lxc.conf
lxc.aa_profile = unconfined
Member

vdloo commented Aug 9, 2016

The lxc.aa_profile == unconfined setting is now baked into the image (>= release-3180)

$ grep aa_profile ~/.vagrant.d/boxes/hypernode_php7/3180/lxc/lxc.conf
lxc.aa_profile = unconfined
@tomlankhorst

This comment has been minimized.

Show comment
Hide comment
@tomlankhorst

tomlankhorst Jul 22, 2017

Contributor

Additionally, it might be possible that a NFS 'timeout' error occurs. This can be caused by the firewall. Allowing the container IP to connect to the host solves this.

sudo ufw allow from 10.0.3.10 or something alike

Contributor

tomlankhorst commented Jul 22, 2017

Additionally, it might be possible that a NFS 'timeout' error occurs. This can be caused by the firewall. Allowing the container IP to connect to the host solves this.

sudo ufw allow from 10.0.3.10 or something alike

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment