Open poxin13 opened 3 years ago
I installed nfs-common on the console and seemed to work after that. Was able to mount manually and via mounts in cloud config.
Hmm. We should not require install to console. Will reopen and investigate this later.
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.
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:
cloud_init: datasources:
network: interfaces: eth1: dhcp_timeout: 0 dhcp: true
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.
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
After upgrading from RancherOS console version to BurmillaOS console version (that was my fault when I did the upgrade...) I cannot longer use NFS mount on nodes.
I see this comment at the beggining, but I don't know how to install nfs-common package, can you explain that?
I installed nfs-common on the console and seemed to work after that. Was able to mount manually and via mounts in cloud config.
Thanks!!
EDIT: Ok, it's so simple... It's enough to perform an apt-get update && apt-get install nfs-common
. Will nfs-common
be included in default BurmillaOS console?
Will nfs-common be included in default BurmillaOS console?
Good question. Based on https://packages.debian.org/buster/nfs-common it looks to be quite small and there is already couple of persons who need it so maybe it would be easiest include lt as part of next update.
It requires some other dependencies and I saw a 26,2 MB installation space in total, so it is not as small as it looks like, but I vote for its addition anyway.
I've just had the same issue, migrated from RancherOS yesterday (as the existing RancherOS docker version didn't support Ubuntu Jammy images as per https://docs.linuxserver.io/faq#jammy ). The upgrade was seamless btw so thanks for that!!
NFS mounts seemed to work fine until I reset the default console via
sudo ros console switch default
as per everyone else the way I had previously gotten NFS to work on RancherOS was as follows in my config:
mounts: - - nasbox.local:/Folder - /NAS - nfs4 - "" services_include: volume-nfs: true
Worked around as above by Installing nfs-common via
EDIT: Ok, it's so simple... It's enough to perform an apt-get update && apt-get install nfs-common. Will nfs-common be included in default BurmillaOS console?
I assume that this will need to be done every-time the console is reset (i.e. every upgrade)?
I assume that this will need to be done every-time the console is reset (i.e. every upgrade)?
Yes if you do console reset as part of upgrade. However it does not happen automatically (like discussed #150 ) so you can choose just updating packages with apt-get update+upgrade like on any Debian based distro.
Or automate that package installation https://burmillaos.org/docs/configuration/advanced/running-commands/ and use reset option.
I've just faced the same NFS problem when trying to deploy a new environment, and I finished in this same issue to realize that I need to install nfs-common
package.
@olljanat will this package finally be included in the base image?
Thanks!!
It is a bit unclear when next version will be released but there is already some other changes waiting in v2.0.2-rc1 so if someone creates pull request about this it will more likely get included.
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)
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.