On 6/21/19 4:10 AM, Jim McGinness wrote:
You've posed an interesting puzzle. My first guess was that there was
just something missing from the box-building process for the 12.0 box.
I finally got my test enviroment back to the point where I could
download the two boxes:
freebsd/FreeBSD-13.0-CURRENT
freebsd-FreeBSD-12.0-RELEASE
to see if I could reproduce your symptoms. As is the nature of things, I
got different symptoms, but they are basically attributable to the fact
that bash is not included in these boxes - a little strange for Vagrant
boxes, since "bash -l" is the default value of config.ssh.shell. In
order to use these boxes with vagrant, your Vagrantfile (or some other
part of your environment) would have to specify a different shell - and
I didn't see you doing this.
But these boxes do come with csh installed, so - if your provisioning
script can be made compatible with csh - you could possibly get past
your problem by adding the line:
config.ssh.shell = "/bin/csh"
to your Vagrantfile.
As to why your v13 box worked and your v12 box didn't, I can't explain.
The boxes on the vagrant cloud get updated from time to time, so I'd
need to be sure I was more exactly getting the same boxes as you did,
and a better characterization of your vagrant environment than you've
given us so far, before I could expect to reproduce what you were
seeing. The fact that you see /usr/local/bin/bash on your boxes is one
indication that your boxes differ in important ways from the ones I just
downloaded.
Thanks for taking the time to investigate this problem. Here's what
we've done in the meantime.
I basically gave up on the FreeBSD-12 box. I went to vagrantup.com and
noticed that there was a newer box called 'generic/freebsd12'. I was
able to call 'vagrant init' on it, then successfully provision it, get
it up, and ssh into it.
This box I believe this box is created by a person whose handle is
'bazinga', as the default hostname for the box was something like
localhost.bazinga. For our application over the past year we used a box
called 'generic/freebsd11' that was also created by bazinga.
Both of his/her 11 and 12 boxes were much more ready-to-use than the
'freebsd/freebsd12' box we were struggling with. For example, bazinga's
boxes come with many ports already installed in /usr/local/bin that the
other box lacked (e.g., perl5). I've been able to provision and
re-provision 'generic/freebsd13' several times and run programs running
as much as 8 hours therein.
So as of now my judgment is that the box about which I posted at the
start of this thread was simply not up to the task. Once we've done a
bit more work on generic/freebsd13 and have started using it in
'production', we'll probably just get rid of the earlier FreeBSD-12 box.
Thank you very much.
Jim Keenan
--
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/5824e4b6-b1c3-f996-6450-6525e201a1f4%40pobox.com.
For more options, visit https://groups.google.com/d/optout.
