Skip to content

Commit

Permalink
Remove reference to vagrant runner in documentation
Browse files Browse the repository at this point in the history
[skip ci]
  • Loading branch information
ivotron committed Jun 6, 2020
1 parent 0bb2306 commit e490b54
Showing 1 changed file with 0 additions and 21 deletions.
21 changes: 0 additions & 21 deletions docs/sections/cn_workflows.md
Original file line number Diff line number Diff line change
Expand Up @@ -277,27 +277,6 @@ popper run --engine singularity
* The use of `ARG` in `Dockerfile`s is not supported by Singularity.
* The `--reuse` flag of the `popper run` command is not supported.

### Vagrant

While technically not a container engine, executing workflows inside a
VM allows users to run workflows in machines where a container engine
is not available. In this scenario, Popper uses [Vagrant][vagrant] to
spawn a VM provisioned with Docker. It then executes workflows by
communicating with the Docker daemon that runs inside the VM. To
execute a workflow in Vagrant:

```bash
popper run --engine vagrant
```

[vagrant]: https://vagrantup.com/

#### Limitations

Only one workflow can be executed at the time in Vagrant runtime,
since popper assumes that there is only one VM running at any given
point in time.

### Host

There are situations where a container runtime is not available and
Expand Down

0 comments on commit e490b54

Please sign in to comment.