Unable to mount NFS

[poxin13]

BurmillaOS Version: (ros os version)
v1.9.0

Where are you running BurmillaOS? (docker-machine, AWS, GCE, baremetal, etc.)
Proxmox KVM

Which console you use (default, ubuntu, centos, etc..)
default

Do you use some service(s) which are not enabled by default?
enabled qemu-guest-agent
enabled volume-nfs

Please share copy of your cloud-init (remember remove all sensitive data first)

hostname: burmilla-docker
mounts:
- - 192.168.1.10:/mnt/zfs-spin-storage
  - /mnt/zfs-spin-storage
  - nfs4
  - ""
rancher:
  console: default
  environment:
    EXTRA_CMDLINE: /init
  network:
    dns:
      nameservers:
      - 192.168.1.1
    interfaces:
      eth0:
        address: 192.168.1.15/24
        dhcp: false
        gateway: 192.168.1.1
  services_include:
    qemu-guest-agent: true
    volume-nfs: true
  state:
    dev: LABEL=RANCHER_STATE
    wait: true
  upgrade:
    url: https://raw.githubusercontent.com/burmilla/releases/v1.9.x/releases.yml

$ system-docker logs console

FINISHED: /sbin/agetty --noclear tty4 linuxtime="2020-12-25T03:11:06Z" level=error msg="Networking not available to load resource"

time="2020-12-25T03:11:06Z" level=error msg="Networking not available to load resource"

mount: /mnt/zfs-spin-storage: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.

time="2020-12-25T03:11:06Z" level=error msg="Failed to mount /mnt/zfs-spin-storage: exit status 32"

[            ] respawn:info: respawn BurmillaOS
built: '2020-12-14T03:55:31Z', v1.9.0
respawn BurmillaOS

Mount has no problem on a standard ubuntu server. Haven't been able to figure this out.

Should I be able to mount this directly from console? Looks like the same error.

rancher@burmilla-docker:/mnt$ sudo mount -t nfs4 -vvvvvv 192.168.1.10:/mnt/zfs-spin-storage /mnt/zfs-spin-storage
mount: /mnt/zfs-spin-storage: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program

[poxin13]

I installed nfs-common on the console and seemed to work after that. Was able to mount manually and via mounts in cloud config.

[olljanat]

Hmm. We should not require install to console. Will reopen and investigate this later.

[olljanat]

Looks that we need also update documentation. Purpose of volume-nfs service (and volume-cifs) is provide NFS/CIFS support for containers with https://github.com/ContainX/docker-volume-netshare

Mounts to console needs nfs-common / cifs-utils to be installed to console.

[msn62]

Mounting a nfs volume is something a lot of users struggled with in Rancheros, including myself.
Finally i found a solution that I would like to share.

WAIT until the network is up during the initiation phase.

This can be accomplished in two ways by editing the file: /var/lib/rancher/conf/cloud-config.d

rancher:
#do a dummy call to a datasource to initiate the network
cloud_init:
datasources:
- url:http://somefile
#or wait until dhcp lease is done
network:
interfaces:
eth1:
dhcp_timeout: 0
dhcp: true
#enable nfs service in systemdocker
service_include:
volume-nfs: true

Both options, initiating the network by a dummy call or wait until a dhcp address is assigned (dhcp_timeout: 0) worked in my case.

Hope this helps somebody. Iam quite a Linux noob btw.

[olljanat]

Mounting a nfs volume is something a lot of users struggled with in Rancheros, including myself.
Finally i found a solution that I would like to share.

WAIT until the network is up during the initiation phase.

Thanks this was useful tip. I guess that we can include some wait network logic to volume-nfs container https://github.com/burmilla/os-services/blob/v1.9.0/images/20-volumenetshare/Dockerfile