Does anybody here have any serious experience creating virtualbox virtual machines in vagrant? I've got a pretty ridiculously simple one, and I can't get port 80 visible from the outside via a host only, bridged, or even forwarded ports set for networking. It's driving me bonkers; if there's anybody out there that may be able to help with this I'd be very grateful to be able to discuss it a bit.
TIA

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

KHELAIR wrote to ALL <=-

Does anybody here have any serious experience creating virtualbox virtual machines in vagrant? I've got a pretty ridiculously simple
one, and I can't get port 80 visible from the outside via a host only, bridged, or even forwarded ports set for networking. It's driving me bonkers; if there's anybody out there that may be able to help with
this I'd be very grateful to be able to discuss it a bit.

Why do you want to do it that way? Just set up your VirtualBox virtual machine in VirtualBox itself. It just seems like you are reinventing the
wheel here.


... The answer is "maybe" ... and that's semi-final
--- MultiMail/Darwin v0.50
þ wcQWK 7.0 ÷ Omicron Theta BBS * Memphis, TN * winserver.us

Re: Re: Vagrant
By: ROBERT WOLFE to KHELAIR on Sat Nov 07 2015 03:16:00

Why do you want to do it that way? Just set up your VirtualBox virtual machine in VirtualBox itself. It just seems like you are reinventing the wheel here.

I'm working in an environment where I need to be able to spin up clones of a development server in the least amount of time possible. Hence fully automated provisioning of a machine from the point of being a raw box just with the OS to a machine fully loaded with a major e-commerce website, database loaded, etc, is my way of avoiding reinventing the wheel, instead of doing it again every time we need another one.
'vagrant up' once the provisioning script is set up correctly and getting a cup of coffee to sip at while it runs is a hell of a lot better than sitting and going through 6-9 hours of loading all of the appropriate crap onto a new virtual machine by hand.
Anyway I got past my vagrant issues. Turns out it was my poor knowledge of iptables that was messing things up. Got that all fixed and working now.

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

On 2015-11-13 08:08 AM, Khelair wrote:

Re: Re: Vagrant
By: ROBERT WOLFE to KHELAIR on Sat Nov 07 2015 03:16:00

Why do you want to do it that way? Just set up your VirtualBox virtual machine in VirtualBox itself. It just seems like you are reinventing the
wheel here.

I'm working in an environment where I need to be able to spin up clones of a
development server in the least amount of time possible. Hence fully automated
provisioning of a machine from the point of being a raw box just with the OS to
a machine fully loaded with a major e-commerce website, database loaded, etc, is my way of avoiding reinventing the wheel, instead of doing it again every time we need another one.
'vagrant up' once the provisioning script is set up correctly and getting a cup of coffee to sip at while it runs is a hell of a lot better than sitting and going through 6-9 hours of loading all of the appropriate crap onto a new virtual machine by hand.
Anyway I got past my vagrant issues. Turns out it was my poor knowledge of iptables that was messing things up. Got that all fixed and working now.

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
� Synchronet � Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

What about Virtual Machine Manager from redHat (yes it is also free and
open source) which uses libvirt. Could you maybe manage it with that in
a script?

---
þ Synchronet þ Electronic Warfare BBS | telnet://bbs.ewbbs.net

On 2016-11-19 08:51 PM, Deavmi wrote:

On 2015-11-13 08:08 AM, Khelair wrote:

Re: Re: Vagrant
By: ROBERT WOLFE to KHELAIR on Sat Nov 07 2015 03:16:00

Why do you want to do it that way? Just set up your VirtualBox

virtual

machine in VirtualBox itself. It just seems like you are

reinventing the

wheel here.

I'm working in an environment where I need to be able to spin up
clones of a
development server in the least amount of time possible. Hence fully
automated
provisioning of a machine from the point of being a raw box just with
the OS to
a machine fully loaded with a major e-commerce website, database
loaded, etc,
is my way of avoiding reinventing the wheel, instead of doing it again
every
time we need another one.
'vagrant up' once the provisioning script is set up correctly and
getting a
cup of coffee to sip at while it runs is a hell of a lot better than
sitting
and going through 6-9 hours of loading all of the appropriate crap
onto a new
virtual machine by hand.
Anyway I got past my vagrant issues. Turns out it was my poor
knowledge of
iptables that was messing things up. Got that all fixed and working now.

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
� Synchronet � Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

What about Virtual Machine Manager from redHat (yes it is also free and
open source) which uses libvirt. Could you maybe manage it with that in
a script?

Also, vmm (virtual machine manager), can also manage QEMU VMs but also
LXE containers.

---
þ Synchronet þ Electronic Warfare BBS | telnet://bbs.ewbbs.net