Vagrant up –no-parallel flag meaning

Do anyone know what exactly vagrant up --no-parallel flag does? I found in the docs that I should use it whenever I am linkink two different containers within same Vagrantfile.

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
    config.vm.define "a" do |app|
        app.vm.provider "docker" do |d|
            d.name = "a"
            d.image = "a"
        end
    end
    config.vm.define "b" do |app|
        app.vm.provider "docker" do |d|
            d.name = "b"
            d.image = "b"
            d.link("a:a")
        end
    end
end

What should I run if I have Vagrantfile looking like this?

  • Recommendation: Deploy Docker application to AWS
  • WordPress 4.8 on Docker REST API Not Accessible
  • prior storage driver “aufs” failed: driver not supported Error starting daemon: error initializing graphdriver: driver not supported
  • Mac OS X, Vagrant, Docker, Nginx, Node - how do ports play together?
  • How to start Phoenix by using PostgeSQL through container?
  • How to use the rabbitmq docker compose yml file to build docker image?
  • vagrant up a --no-parallel && vagrant up b
    

    or

    vagrant up a && vagrant up b --no-parallel
    

    or

    vagrant up --no-parallel
    

    ?

  • Save a file generated by app running on docker to a given path in the host machine
  • Service 'web' failed to build: lstat apache/sites-enabled/000-default.conf: no such file or directory
  • Rebuild Docker container on file changes
  • “Installing Docker: FAILED” Error on setup with Meteor-Up and Debian 7 wheezy
  • Why does docker compose exit right after starting?
  • Secure server with Fail2ban and Docker
  • One Solution collect form web for “Vagrant up –no-parallel flag meaning”

    --no-parallel option makes sense when vagrant up is used to bring multiple machines up altogether: that is when Vagrantfile declares multiple machines and vagrant up is either given no machine names or multiple machine names. In this case, if the provider supports this (and yes, Docker provider does indeed), Vagrant will attempt to bring all requested machines up in parallel, unless --no-parallel is given.

    So with Docker provider, when linking containers, one may use --no-paralel when bringing multiple machines up altogether:

    $ vagrant up --no-parallel
    

    or

    $ vagrant up /regex to match machine names/ --no-parallel
    

    However, if you bring machines up one-by-one with separate commands, it will have no effect (no harm either) if --no-parallel is specified or not. So one may simply do:

    $ vagrant up a && vagrant up b
    
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.