Vagrant Feature Preview: Docker-Based Development Environments
1–10 of 60 posts
Re: Vagrant Feature Preview: Docker-Based Development Environments
#2Fantastic! Was just about to look into using docker with our current vagrant workflow.
Re: Vagrant Feature Preview: Docker-Based Development Environments
#3This is really cool. It'd be great to be able to piece together development environments from dockerfiles even quicker than you can now.
One of the great things about docker is that once you've played about for an hour or so you've already picked up most of it. It's not like Chef or Puppet – configuring environments using VirtualBox and a VM is really simple. I wonder how fast this will make things.
Re: Vagrant Feature Preview: Docker-Based Development Environments
#4Vagrant was a huge step forward for managing vm environments, but I'm afraid its integration with Docker is forced and misguided.
For instance, the idea of ssh provisioner does not jive with Docker. The better approach is run the container with shared volume, and run another bash container to access the shared volume. If you are just starting to look at Docker, I would recommend to use Vagrant to provision the base image, and leave the heavy lifting to Docker itself.
Re: Vagrant Feature Preview: Docker-Based Development Environments
#5Vagrant was a huge step forward for managing vm environments, but I'm afraid its integration with Docker is forced and misguided. For instance, the idea of ssh provisioner does not jive with Docker. The better approach is run the container with shared volume, and run another bash container to access the shared volume. If you are just starting to look at Docker, I would recommend to use Vagrant to provision the base i…
What you described is actually the default way the Docker provider works, which aligns with the best-practice of how Docker is used: you can launch a set of single-process containers that don't support SSH, but have volumes mounted, links, etc. Then you use `vagrant docker-run` to launch one-off containers with bash, or run scripts, etc. The first two videos and examples show this.
To be clear: see the first example Vagrantfile that is in the blog post. Then read down further and see `docker-run`. You can use that to launch another container to get a bash prompt. This is _exactly_ the workflow you describe.
We built exactly for this. :)
We also support SSH-based containers, but you can see that it is explicitly opt-in (you must set "has_ssh" to "true"), also showing that it really isn't the normal way things are done.
Vagrant is about flexibility, and we surface both use-cases.
Re: Vagrant Feature Preview: Docker-Based Development Environments
#6Vagrant was a huge step forward for managing vm environments, but I'm afraid its integration with Docker is forced and misguided. For instance, the idea of ssh provisioner does not jive with Docker. The better approach is run the container with shared volume, and run another bash container to access the shared volume. If you are just starting to look at Docker, I would recommend to use Vagrant to provision the base i…
Yeah, part of me was thinking that too. Use container volumes. Use dockerfiles. And don't all containers support lxc-attach (as opposed to SSH?).
I didn't want to be negative -- it'd be great to be able to have an environment set up in 10 seconds with vagrantfiles -- so until then I'm trying to see the positives.
Re: Vagrant Feature Preview: Docker-Based Development Environments
#7What's the ETA for 1.6?
Re: Vagrant Feature Preview: Docker-Based Development Environments
#8I've been looking for a way to integrate docker into my existing workflow. This integration takes nothing away from Docker and just makes Vagrant that much more flexible and valuable to teams already using it and newcomers. Can't wait to run this through its paces.
Curious, how is the default "proxy" vm on macs sized?
Re: Vagrant Feature Preview: Docker-Based Development Environments
#9So when is this going to be hooked up with consul for a bit more magic?
Re: Vagrant Feature Preview: Docker-Based Development Environments
#10I currently have an ansible script which can set up a web-service on any Debian/Ubuntu box, and can be invoked
1) over SSH, or 2) by Vagrant when provisioning a VM.
Docker, on the other hand, provisions it's containers from a rather simplistic Dockerfile, which is just a list of commands. The current solution to provision a container through ansible is rather messy[1], and shows that Docker's configuration doesn't display the same separation-of-responsibilities as Vagrant's does.
Luckily, this lets me use Docker as another provider through the Vagrant API. Woooo!
http://www.ansible.com/blog/2014/02/12/installing-and-buildi...