You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to change the IP to allow the NFS, but does not take effect.
I set the 192.168.10.0/24, why not take effect?
My configure is follows:
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 bbee608d-90af-47ac-8553-42e641905074"/data/my_vagrant/vagrant-dev-php55/workspace"192.168.10.10(rw,no_subtree_check,all_squash,async,insecure,anonuid=1000,anongid=1000,fsid=2040498797)# VAGRANT-END: 1000 bbee608d-90af-47ac-8553-42e641905074
# -*- mode: ruby -*-# vi: set ft=ruby :# All Vagrant configuration is done below. The "2" in Vagrant.configure# configures the configuration version (we support older styles for# backwards compatibility). Please don't change it unless you know what# you're doing.Vagrant.configure("2")do |config|
# The most common configuration options are documented and commented below.# For a complete reference, please see the online documentation at# https://docs.vagrantup.com.# Every Vagrant development environment requires a box. You can search for# boxes at https://atlas.hashicorp.com/search.config.vm.box="CentOS72 x86_64 minimal"# Disable automatic box update checking. If you disable this, then# boxes will only be checked for updates when the user runs# `vagrant box outdated`. This is not recommended.# config.vm.box_check_update = false# Create a forwarded port mapping which allows access to a specific port# within the machine from a port on the host machine. In the example below,# accessing "localhost:8080" will access port 80 on the guest machine.# config.vm.network "forwarded_port", guest: 80, host: 8080# Create a private network, which allows host-only access to the machine# using a specific IP.config.vm.network"private_network",ip: "192.168.10.10"# Create a public network, which generally matched to bridged network.# Bridged networks make the machine appear as another physical device on# your network.config.vm.network"public_network",bridge: "eth0"# Share an additional folder to the guest VM. The first argument is# the path on the host to the actual folder. The second argument is# the path on the guest to mount the folder. And the optional third# argument is a set of non-required options.# config.vm.synced_folder "../data", "/vagrant_data"config.vm.synced_folder"./workspace/","/vagrant",allow_ip: "192.168.10.0/24",:nfs=>true,:linux__nfs_options=>['rw','no_subtree_check','all_squash','async','insecure']# Provider-specific configuration so you can fine-tune various# backing providers for Vagrant. These expose provider-specific options.# Example for VirtualBox:## config.vm.provider "virtualbox" do |vb|# # Display the VirtualBox GUI when booting the machine# vb.gui = true## # Customize the amount of memory on the VM:# vb.memory = "1024"# end## View the documentation for the provider you are using for more# information on available options.# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies# such as FTP and Heroku are also available. See the documentation at# https://docs.vagrantup.com/v2/push/atlas.html for more information.# config.push.define "atlas" do |push|# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"# end# Enable provisioning with a shell script. Additional provisioners such as# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the# documentation for more information about their specific syntax and use.# config.vm.provision "shell", inline: <<-SHELL# apt-get update# apt-get install -y apache2# SHELLconfig.vm.provision"ansible"do |ansible|
ansible.inventory_path="provisioning/inventory.ini"ansible.playbook="provisioning/playbook.yml"ansible.limit="all"# ansible.raw_arguments = [# "--connection=paramiko",# "--private-key=/data/my_vagrant/vagrant-dev-php55/.vagrant/machines/default/virtualbox/private_key"# ]endconfig.vm.provision"shell",inline: <<-SHELL systemctl disable firewalld systemctl stop firewalld SHELLend
Where did you read about this :allow_ip option? Looking at the source, there's no mention of it and it's not mentioned in the Vagrant documentation either from the look of it.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 3, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to change the IP to allow the NFS, but does not take effect.
I set the 192.168.10.0/24, why not take effect?
My configure is follows:
cat /etc/exports
Vagrantfile with nfs folder:
Vagrant version
vagrant: 1.8.4
Host operating system
Ubuntu 14.04.4 LTS
Guest operating system
virtualbox: 5.0.24
os: CentOS 7.2 Minimal
Vagrantfile
Debug output
Expected behavior
What should have happened?
Actual behavior
What actually happened?
Steps to reproduce
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
The text was updated successfully, but these errors were encountered: