Vagrant: manage Docker + VirtualBox easily

| 0 comments

5.00 avg. rating (91% score) - 1 vote

As you may know, I’m using Vagrant for more than a year now with VirtualBox. Docker is a faster alternative that needs to be taken into consideration. Having the possibility to manage both of them with the same tool can be very interesting. For information, I mainly use it with VirtualBox because it’s any platform compatible and Docker because it’s perfect for a CI like Jenkins.

I recently talked about my implication into the Smash project. I made a Vagrantfile for it. I encounter several problems and it took time for me to resolve them. I’m going to share with you my experience on it. I’m going to describe the Vagrantfile and then, I’ll give the full version of it. The first part:

I’m using here some vars that can be override with Shell environment vars. For example, before launching Vagrant, you can update a default var like this:

Or you can simply export them to keep them in your current session.

The VAGRANT_DEFAULT_PROVIDER var is a little bit more complex. I needed to do that because of this part:

I encountered a problem with Docker provider, because the “config.vm.provider” line is not like a if statement (like I thought at the beginning). That mean the Vagrantfile is fully parsed anytime you call it and all options are set. The problem was on the “config.vm.box” option which was used for Docker provider as well and was overriding the Docker image parameter I was trying to use. This produced a fail resolution of the required image to deploy. That’s why I’m using the if statement and had to use a specific var for it.

Now regarding the Docker part:

As you can see, some options are commented. That’s because I prefer using “d.image” instead of a Dockerfile (d.build_dir) but can’t make it work for the moment. I prefer using the commented lines because I can use a use vars with the Vagrantfile instead of a static Dockerfile. However, for an unknow reason (for the moment), I encounter SSH issue when not using the Dockerfile (I’ll dig into it and let you know in future a post). So here is the Dockerfile:

You noticed there is nothing very interesting in it, I mean nothing that Vagrant cannot handle. That’s why I need to dig into this last issue. You may notice that I’m using a custom image. This image has been built with a SSH server of course to start it once Vagrant will boot a Docker container. This is necessary to have it if you want to use a provisioner like Ansible (will talk about it in next posts too).

The last part is talking about the machine declaration:

Easy to understand, the web1 machine will be used with a bridged connexion and a certain amount of RAM.

To finish, here is the Vagrantfile with all parts:

Now if I want to start a VM (web1) with VirtualBox and a SQL (sql1) with Docker, I can do like this:

Easy right ?! :-).
Note 1: You do not need to specify this variable for VirtualBox as this is the default one.
Note 2: I did not export all Docker required ports etc…because this is not the object of the post here.

Hope you’ve enjoyed this post. If it’s the case, you’ll enjoy next ones.

Author: Deimos

I'm a passionate DevOps. I love transmit my skills and I love working on high availability infrastructures/technologies.

Laisser une réponse