Sorry to reply to my own post, but I realize now that my Vagrantfile is
being executed. Just didn't look like it since it couldn't find the
cookbook files and therefore the output looked boilerplate. However, I am
still left with cookbook files that are not being found and therefore the
box isn't being provisioned. If I manually untar the cookbook files from
the *.box file, everything works as expected. But I feel like manual steps
to unpack the cookbook files is not the behavior I should expect, and
therefore I believe am still doing something wrong.
On Friday, November 16, 2018 at 10:11:12 AM UTC-5, Nc Diesel wrote:
>
> So I package a box:
>
> vagrant package --base MyDevelopment --output MyDevelopment-0.5.0.box
> --include cookbooks --vagrantfile Vagrantfile
>
> When I untar the box, cookbooks and its entire tree and the correct
> Vagrantfile are in there. So far so good
>
> But no combination of "vagrant box add" and "vagrant init" that I can find
> will create box with the cookbooks directory tree nor does it
> create/overwrite the Vagrant file with the Vagrantfile packaged with the
> box.
>
> Any ideas what in the heck I am doing wrong??
>
> Thanks in advance!
>
>
>
--
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/a405b3c0-0c7d-40bc-ac10-9ec56a39de17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
