Building Vagrant VMWare box on EC2 Ubuntu Instance

61 views
Skip to first unread message

Moogs

unread,
Oct 21, 2016, 6:16:44 PM10/21/16
to Packer
Hello,

We are looking at setting up a build pipeline that spawns a bunch of different images for different environments. Specifically EC2 and Vagrant under Fusion images (AMI/Box). I am trying to build a vagrant box image for vmware fusion on Ubuntu in EC2 but it seems this is futile as it requires a lot of the VMWare tools and such. Is this even possible? What is the recommended approach to building images (AMI for EC2 and Vagrant/Fusion for local dev work)?

Thanks!

Moogs

Nick Charlton

unread,
Oct 21, 2016, 6:41:27 PM10/21/16
to Packer
Hi!

This isn't something I've directly tried to do with EC2, as I've only done this kind of thing on other virtualisation platforms.

You'd need to have support for nested virtualisation (Intel v-T, is perhaps the right name?), which I don't believe EC2 supports (see: http://cloudstacking.com/posts/running-hyper-v-vmware-or-xen-on-an-aws-ec2-instance.html).

Nick

Alvaro Miranda Aguilera

unread,
Oct 21, 2016, 7:06:53 PM10/21/16
to packe...@googlegroups.com
 can you share a bit of info on why you want 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/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/c1fb3b0b-267b-4d0b-9d9b-cd2dabd3dcba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Moogs

unread,
Oct 21, 2016, 8:04:43 PM10/21/16
to Packer
Our entire infra is on EC2. We want to tie in an image building process for production images to the same system that builds dev images. We use S3 to store boxes now but they're hand built. We would ideally like to keep our build infra in EC2 and not have to push to a slave in our office running os x or something similar. All of our instances are automated including build slaves and such. We would like to keep things under the same fold if possible.


On Friday, October 21, 2016 at 4:06:53 PM UTC-7, Alvaro Miranda Aguilera wrote:
 can you share a bit of info on why you want that?
On Sat, Oct 22, 2016 at 12:16 AM, Moogs <moo...@gmail.com> wrote:
Hello,

We are looking at setting up a build pipeline that spawns a bunch of different images for different environments. Specifically EC2 and Vagrant under Fusion images (AMI/Box). I am trying to build a vagrant box image for vmware fusion on Ubuntu in EC2 but it seems this is futile as it requires a lot of the VMWare tools and such. Is this even possible? What is the recommended approach to building images (AMI for EC2 and Vagrant/Fusion for local dev work)?

Thanks!

Moogs

--
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/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.



--
Alvaro

Alvaro Miranda Aguilera

unread,
Oct 22, 2016, 11:36:25 AM10/22/16
to packe...@googlegroups.com
sorry, just to have the whole picture

if all your infra is on EC2, where the vmware requirement came from?


To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/b69b0394-8023-44f1-b305-edcde31d3dbd%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Moogs Nonamer

unread,
Oct 22, 2016, 1:43:50 PM10/22/16
to packe...@googlegroups.com
As mentioned in the original post, local Dev work.
You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/sO28Zjr_Jos/unsubscribe.
To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ez38H9d-z0%3DjWmsYQ2-6DvGZRLKh9X4EruV63sUEj5nyw%40mail.gmail.com.

Alvaro Miranda Aguilera

unread,
Oct 22, 2016, 2:09:51 PM10/22/16
to packe...@googlegroups.com
Thanks for the confirmation.

Packer support creating VMWare VMs for Vagrant and AWS.

If you are creating AWS AMI for Vagrant, then packer can do that too.

The original scope of packer was to have the same provisioning script running on several providers, say Fusion and AWS AMI.

With this in mind, you will end having a box that has been provisioned in the same way.

So is not neeed to have cross hypervisor stuff.

Of course there are usercases when people would love to do differently.

In the particular case you have, even if you could install vmtools inside an AMI, packer doesn't have a way to download a disk or AMI and create a VM for Fusion from that.

So I am afraid that the use case is out side of what packer can do today.

Alvaro.

To unsubscribe from this group and all its topics, send an email to packer-tool+unsubscribe@googlegroups.com.

--
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/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Reply all
Reply to author
Forward
0 new messages