Vagrant: Difference between revisions
imported>Mic92 document vagrant quirk |
imported>Lheckemann No edit summary |
||
Line 13: | Line 13: | ||
# Minimal configuration for NFS support with Vagrant. | # Minimal configuration for NFS support with Vagrant. | ||
services.nfs.server.enable = true; | services.nfs.server.enable = true; | ||
networking.firewall.extraCommands = '' | |||
networking.firewall. | ip46tables -I INPUT 1 -i vboxnet+ -p tcp -m tcp --dport 2049 -j ACCEPT | ||
''; | |||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
This | This should make NFS mounts work. | ||
{{note| | {{note|Vagrant will, by default, want to use <code>sudo</code> and modify <tt>/etc/exports</tt>. As long as you are not defining exports with <tt>configuration.nix</tt>, vagrant should be able to work.}} | ||
{{note|Home directories are set not to be world-searchable by default on NixOS. This may lead to a "permission denied" error when trying to mount directories within your home into the VM. You can change this by running <code>chmod a+x ~</code>, but note that this will allow all users on the system to read world-readable files within your home given the paths.}} | |||
== Plugins == | == Plugins == |
Revision as of 12:14, 7 January 2019
NixOS as Host
Using NFS mounts
Add to your configuration.nix:
{
# Minimal configuration for NFS support with Vagrant.
services.nfs.server.enable = true;
networking.firewall.extraCommands = ''
ip46tables -I INPUT 1 -i vboxnet+ -p tcp -m tcp --dport 2049 -j ACCEPT
'';
}
This should make NFS mounts work.
Plugins
NixOS Plugin
See the NixOS vagrant box page, which as information about the vagrant-nixos-plugin
project.
Troubleshooting: conflicting dependencies bundler when installing vagrant plugins
As of 18.03 vagrant plugins are broken:
$ vagrant plugin update
Updating installed plugins...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
conflicting dependencies bundler (= 1.14.6) and bundler (= 1.16.1)
Activated bundler-1.16.1
which does not match conflicting dependency (= 1.14.6)
Conflicting dependency chains:
bundler (= 1.16.1), 1.16.1 activated
versus:
bundler (= 1.14.6)
Gems matching bundler (= 1.14.6):
bundler-1.14.6
using the following nix expression fixes the problems:
(import <nixpkgs> {
overlays = [
(self: super: {
bundler = super.bundler.overrideAttrs (old: {
name = "bundler-1.16.1";
src = super.fetchurl {
url = "https://rubygems.org/gems/bundler-1.16.1.gem";
sha256 = "1s2nq4qnffxg3kwrk7cnwxcvfihlhxm9absl2l6d3qckf3sy1f22";
};
});
})
];
}).vagrant
More information in this issue