I've been using Vagrant extensively. So I know the difference between init
and up.
My problem is the following:
- I created a box myself, by packaging an image, together with a
Vagrantfile and a Metadata.json file.
- In that Vagrantfile I have the following content:
Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
libvirt.disk_bus = 'virtio'
end
config.vm.synced_folder ".", "/vagrant", disabled: true
end
So I tarred/ziped those three files in to a new box, and imported that in
to Vagrant.
Then I tested this. I created a new directory, and in that directory I did:
vagrant init newbox
vagrant up
What I expected to happen:
The box is started, but no synced folder is setup.
What I got:
Box is started, and vagrant attempts to setup a synced folder, which fails
on this particular image. (and this is why I want it to be disabled by
default)
In other words, I expect (and the documentation has led me to expect this)
that the config you put in the Vagrantfile you package in a box is
interpreted as a default for that box, and that this config is merged with
the Vagrantfile created by vagrant init in your working directory. In other
words, I expect to be able to set defaults in a box.
Are my expectations incorrect? Or did I do something wrong? Or is this a
bug?
On Friday, 7 July 2017 17:47:38 UTC+1, Salty Vagrant wrote:
>
> I suspect this is simply a misunderstanding of the vagrant commands.
>
> Once you have your edited Vagrantfile (with the synced_folder disabled)
> you should use ‘vagrant up’ NOT ‘vagrant init’.
>
> ‘vagrant init’ creates a new Vagrantfile and sets the vm/box to the value
> you provide on the command line (this will overwrite the one you previously
> created).
>
> ‘vagrant up’ on the other hand will start the VM specified by the
> Vagrantfile.
>
> On 7 Jul 2017, at 16:44, Krist van Besien wrote:
>
> Hello all,
>
> I created my own box, and the box, and the Vagrantfile included in the box
> has the following content:
>
> Vagrant.configure("2") do |config|
> config.vm.provider :libvirt do |libvirt|
> libvirt.disk_bus = 'virtio'
> end
> config.vm.synced_folder ".", "/vagrant", disabled: true
> end
>
>
> However this setting is ignored. After doing a "vagrant init <mybox>" I
> need to edit the Vagrantfile manually to again disable the synced folder.
>
> Why is that?
>
>
>
>
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com
>
> <https://groups.google.com/d/msgid/vagrant-up/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/5345e486-c18f-4d34-93a3-62b03e557dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
