From d404ff926aebde791d17445adbd3cf65e86c3839 Mon Sep 17 00:00:00 2001 From: sophia Date: Wed, 26 Oct 2022 16:18:23 -0500 Subject: [PATCH] Clarify using 'vagrant up name' must be run from within a Vagrant project --- website/content/docs/cli/up.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/content/docs/cli/up.mdx b/website/content/docs/cli/up.mdx index 43b52902b..772e6bbdb 100644 --- a/website/content/docs/cli/up.mdx +++ b/website/content/docs/cli/up.mdx @@ -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.