Open jtlayton opened 6 years ago
First, long time no see, Jeff!
Second, this request seems entirely reasonable. Thanks for the suggestion!
Hah, yes! Hope you're doing well, Thomas!
FWIW, my main interest here is that I'm working on a clustered NFS server that runs under k8s, and this makes it hard to use the standard NFS port as a NodePort.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
The buildroot configuration for this is NFS_UTILS_INSTALL_INIT_SYSTEMD
ln -fs ../../../../usr/lib/systemd/system/nfs-server.service \
$(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/nfs-server.service
@afbjorklund @tstromberg any decision whether we want this service to be disabled by default ?
Yeah this seems reasonable honestly.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
Please provide the following details:
Environment:
Minikube version (use
minikube version
): v0.28.2cat ~/.minikube/machines/minikube/config.json | grep DriverName
): kvm2cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): v0.28.1On startup, minikube starts up knfsd (via the nfs-server.service under systemd), even though it serves no exports. This makes it somewhat useless -- it should not start the nfs server unless it has something to serve:
When constructing the ISO, could we add in a call to "systemctl disable nfs-server" to ensure that it's not started by default?