Skip to content

Commit

Permalink
Clarify using 'vagrant up name' must be run from within a Vagrant pro…
Browse files Browse the repository at this point in the history
…ject
  • Loading branch information
soapy1 committed Oct 26, 2022
1 parent 9aae935 commit d404ff9
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions website/content/docs/cli/up.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,13 @@ This command creates and configures guest machines according to your
[Vagrantfile](/docs/vagrantfile/).

This is the single most important command in Vagrant, since it is how
any Vagrant machine is created. Anyone using Vagrant must use this command
on a day-to-day basis.
any Vagrant machine is created.

## Options

- `name` - Name of machine defined in [Vagrantfile](/docs/vagrantfile/)
- `name` - Name of machine defined in [Vagrantfile](/docs/vagrantfile/). Using
`name` to specify the Vagrant machine to act on must be done from within a
Vagrant project (directory where the Vagrantfile exists).

- `id` - Machine id found with `vagrant global-status`. Using `id` allows
you to call `vagrant up id` from any directory.
Expand Down

0 comments on commit d404ff9

Please sign in to comment.