b2 install threading=multi link=static -with-thread -with-system cd. b2 stage threading=multi link=static -with-thread -with-system. rm -Rf cmake-3.22.2 cmake -version else echo 'Found CMake!' cmake -version fi if then mkdir boost cd boost wget -nv tar xfz boost_1_78_0.tar.gz cd boost_1_78_0/. bash_aliases which cmake >/dev/null if then wget -nv tar -xzvf cmake-3.22.2.tar.gz rm cmake-3.22.2.tar.gz cd cmake-3.22.2. # -*- mode: ruby -*- # vi: set ft=ruby : $script =. Copy the content below AND fill in your credentials in the right places (look for ) Your 'Vagrantfile' should look like this. Setup Vagrant Vagrantfile (up-to-date February 2022)

Although for Docker a similar experience can be created as well.

VSC offers a good developers experience working with Remote Development.

So it depends on how much your OS'es really vary, but 'Windows', 'Ubuntu64' and 'Debian32' (for a PI for example) does not fly with Docker.

With multiple VM's you can run multiple OS'es, while Docker uses a single kernel.

Not as easy to 'suspend' a container as a VM (not the goal of Docker anyway).

So you can not run both VirtualBox and Docker for Windows (and/or WSL2).Only 1 'program' can utilize the VT-x/VT-d features of the processor to run a Hypervisor.

I do run other Virtual Machines as well with Virtual Box.

Docker on Windows is/was not the best target for Docker yet.

I guess you can probably re-create an almost identical experience with Docker although I have not tried that myself for several reasons (at the moment):

Don't worry about having to do all kind of housekeeping to keep things clean.

You can freely fool around in your environment without worrying to mess it up.

Just update the Vagrant file provision parts.

Real easy to update main libraries and/or build tools (new CMake version or Boost libraries, etc.).

It becomes easy to update the underlying OS (for example from Debian Stretch to Debian Buster).

One command to recreate a whole new and clean environment.

One command to fully throw away your whole (messed-up) environment.

No seriously, that is the biggest advantage and this is why: The biggest reason and advantage of using Vagrant for your development environment is that you can destroy it :)

2.1 Vagrantfile (up-to-date February 2022).

Vagrant up provider virtualbox