Docker File Sharing Performance Code Right Away
Docker File Sharing Performance Software Before Making

Vagrant up goes through the entire process of configuring the vm, running the application, and running tests (like performing API calls).

Press question mark to learn the rest of the keyboard shortcuts Log in sign up User account menu 6 Docker vs Vagrant for performance on MacBook.

Currently I work on a windows PC and use oracle virtual box with an ubuntu guest (with gui) which is becoming painfully slow.

Ive looked into docker, is it only fast on linux hosts I see for OSX you run docker with a small vm called docker toolbox: 11 comments share save hide report 75 Upvoted This thread is archived New comments cannot be posted and votes cannot be cast Sort by best level 1 13 points 4 years ago If you deploy to VMs use vagrant.

Thats more important than the negligible performance difference.

Boot2DockerDocker toolbox are actually small VMs.

Highly optimized to be sure, but VMs none the less so your performance will vary just like it did on your windows machine.

I have found that the boot2docker vms are pretty speedy but this mainly relies on your host system specs, CPURAM.

I actually use both Docker and Vagrant depending on the situation.

Sometimes I want to replicate full nodes so I use vagrant and vbox, sometimes I only need an execution environment so I use Docker.

I use Vagrant for testing server configuration or playing with an entire environment.

But my Mac has little problem running a few VMs.

By default if you run rocker on a mac youre running it inside a virtualbox vm just like vagrant.

As others have pointed out, docker wont run natively on macbook, so you have to do it through virtual machine anyways.

But reading your post, youre going to want to read up more on how vagrant works.

You create a Vagrantfile which creates a vm and runs some type of provisioner (shell script, puppet, chef, salt) that configures the vm with all of your dependencies.

When you type vagrant up in your project directory, a VM starts up, gets configured, and gets everything ready to run your application.

Now, if youre just looking to spin up a vm and use it for all those linux apps, then vagrant is not for you.

The purpose of vagrant is that, once you set it up, a fellow developer (and that can include yourself on a second machine, or 3 months after you last worked on the project) can download your code, type vagrant up, and be able to run the code right away.

Its a bit of a pain to setup each vm, but it forces you to think how someone else will run your code.

If you destroy and recreate your vm, it has to work perfectly.

If you have dependencies of apachephplibgd, then a bash script could install those.

You could have have an example apache configuration file (say with redirects) that works for your application.

If you have an example database you use for development work, you can have your bash script load that into the database.

Some advanced thoughts: In my environment, we use Vagrant to test software before making a package.

When we check code into the git repo, that code gets checked out and make test is ran.

Docker File Sharing Performance Code Right Away

Docker File Sharing Performance Software Before Making

Docker For Mac File Sharing Performance