(I am new to Docker and Boot2Docker, but I did one project with Vagrant for
smoothing the test environment)
I am working on a webapp (3 tier architecture) and my goal is to have the
devop-related code become reusable for the most for 1) production on AWS 2)
production on docker-ready machines (without hypervisor layer), 3)
development-testing loop in my local machine.
Here is my thought of using Vagrant + Boot2Docker + Dockerfile:
1) Use Vagrant + Virtualbox (Boot2Docker) for local development, Vagrant
+ AWS (AMI) for AWS deployment
-- hopefully my Vagrantfile can be kept almost same (probably
some minor changes because the 'box' will be different such as this line:
machine.vm.box
= "precise64")
2) Dockerfile is a reusable way regardless whether container lives on
top of bare-OS or on top of VM.
-- hopefuly my Dockerfile can be kept almost same, or maybe
exactly same.
So from the deployment run time scenario perspective:
1) For development loop (local machine), it would be Vagrant (with
Virtualbox as provider) + Boot2Docker (as VM) + Container (inside
Boot2Docker)
2) For AWS deployment (AWS EC2), it would be Vagrant (with AWS as
provider) + AMI (as VM) + Container (inside AMI)
3) For bareOS deployment, it would be Vagrant (with Docker as provider)
+ Container (directly)
Thanks,
Sean
--
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].
For more options, visit https://groups.google.com/d/optout.
