Starting a project 16
| Command | What it does |
|---|---|
vagrant init | Create a VagrantfileWrites a starter Vagrantfile in the current directory unless one already exists there. |
vagrant init NAME | Create a Vagrantfile for a boxThe first argument is written into the config.vm.box setting of the new file. |
vagrant init NAME URL | Set the box and its URLThe second argument is written into the config.vm.box_url setting of the Vagrantfile. |
vagrant init --minimal | Skip the instructional commentsProduces a short Vagrantfile without the explanatory comments; the short form is -m. |
vagrant init --force | Overwrite an existing VagrantfileReplaces the Vagrantfile already present at the current path. |
vagrant init --box-version VERSION NAME | Pin the box versionPuts a version number or a constraint such as "> 0.1.5" for the box into the generated file. |
vagrant init --output FILE | Write the Vagrantfile elsewhereSaves the result under the given file name; a single dash sends it to standard output instead. |
vagrant init --template FILE | Use a custom templateGenerates the Vagrantfile from your own ERB template. |
vagrant validate | Check the VagrantfilePrints "Vagrantfile validated successfully." when the file is structured correctly. |
vagrant validate --ignore-provider | Skip provider settingsLeaves provider-specific configuration options out of the check. |
vagrant version | Show installed and latest versionMakes a network call to look up the newest release that is available. |
vagrant --version | Show the installed version onlyPrints the local version number without contacting the network. |
vagrant -h | List the common commandsPrints the primary subcommands with a one-line summary of each. |
vagrant COMMAND -h | Show help for one commandPrints that command's usage line and every flag it accepts. |
vagrant list-commands | List every subcommandIncludes the ones hidden from the basic help, such as rsync and docker-exec. |
vagrant autocomplete install --bash --zsh | Install shell completionTurns on tab completion of Vagrant commands; these two shells are the ones currently supported. |
Bringing machines up and down 18
destroy leaves the box on disk; removing it as well takes vagrant box remove.
| Command | What it does |
|---|---|
vagrant up | Create and start the machinesBuilds and configures the guest machines described in the Vagrantfile. |
vagrant up NAME | Start one named machineTakes a machine name from the Vagrantfile; this form only works inside the project directory. |
vagrant up ID | Start a machine by its IDThe ID comes from global-status, so no change of folder is needed first. |
vagrant up /follower[0-9]/ | Start machines matching a patternA machine name written between forward slashes is treated as a regular expression. |
vagrant up --provider PROVIDER | Choose the providerRuns the new machine on the named provider rather than the default one. |
vagrant up --[no-]parallel | Toggle parallel start-upWith --parallel several machines start at once where the provider allows; --no-parallel starts them one by one. |
vagrant up --[no-]destroy-on-error | Keep or destroy after a failureBy default a machine that fails fatally on its first up is destroyed; the --no- form keeps it. |
vagrant up --[no-]install-provider | Toggle provider auto-installControls whether Vagrant tries to install a requested provider that is missing. |
vagrant halt | Shut the machine downVagrant tries the guest's own shutdown mechanism first and cuts power only if that fails. |
vagrant halt --force | Power off immediatelySkips the graceful shutdown attempt, like unplugging the guest. |
vagrant suspend | Suspend the machineSaves the exact running state to disk so the guest stops using host RAM and CPU. |
vagrant suspend --all-global | Suspend every running machineActs on VMs across the whole system instead of one environment; the short form is -a. |
vagrant resume | Resume a suspended machineContinues from the saved point instead of doing a full boot. |
vagrant destroy | Delete the machineStops the machine and removes everything Vagrant created for it; the downloaded box stays installed. |
vagrant destroy --force | Skip the confirmation promptDeletes at once instead of asking you to confirm first. |
vagrant destroy --graceful | Shut down before destroyingPowers the VM off cleanly first; the short form is -g. |
vagrant destroy --[no-]parallel | Toggle parallel destroyRemoving several machines at once needs provider support and switches on --force by itself. |
vagrant destroy ID | Destroy a machine from anywherePass an ID printed by global-status, such as a1b2c3, to remove a machine without changing directory. |
Provisioning and reload 11
| Command | What it does |
|---|---|
vagrant provision | Run the provisionersWorks on a running machine, which makes it a quick way to test changes to provisioning scripts. |
vagrant provision --provision-with X,Y,Z | Run selected provisioners onlyTakes a comma-separated list of provisioner types or names; the rest are skipped. |
vagrant up --provision | Force provisioning on upProvisioners normally run only on the first up; this runs them again. |
vagrant up --no-provision | Start without provisioningBrings the machine up and leaves every provisioner out, even ones set to run always. |
vagrant up --provision-with X,Y,Z | Start with chosen provisionersLimits the run to the listed provisioners while the machine is brought up. |
vagrant reload | Restart and re-read the VagrantfileEquivalent to a halt followed by an up; needed for Vagrantfile changes to take effect. |
vagrant reload --provision | Restart and provisionReloads the configuration and also runs the provisioners, which a plain reload leaves out. |
vagrant reload --no-provision | Restart without provisioningStops provisioners configured for every reload from running this time. |
vagrant reload --provision-with X,Y,Z | Restart with chosen provisionersAfter the restart only the listed provisioner types or names are executed. |
vagrant reload --force | Restart with a hard power-offSkips the graceful shutdown during the halt half of the reload. |
vagrant resume --provision | Resume and provisionRuns the provisioners again after waking the machine, which resume skips by default. |
Connecting to a machine 18
| Command | What it does |
|---|---|
vagrant ssh | Open an SSH sessionLogs in to the running machine and gives you a shell; a single-machine project needs no name. |
vagrant ssh NAME | SSH into a named machineIn a multi-machine setup use the name that vagrant status prints, such as node1. |
vagrant ssh ID | SSH into a machine by IDReaches a machine of another Vagrant project with the ID that global-status lists. |
vagrant ssh -c COMMAND | Run one command over SSHPrints the command's output and returns to the host instead of opening a shell. |
vagrant ssh --plain | SSH without Vagrant's authenticationConnects in plain mode, so supplying the credentials is left to you. |
vagrant ssh -- EXTRA_SSH_ARGS | Pass extra arguments to sshEverything after the two hyphens goes straight to the ssh executable, for example to set up a reverse tunnel. |
vagrant ssh-config | Print an SSH config entryThe output can go into an SSH config file so that plain ssh reaches the machine directly. |
vagrant ssh-config --host NAME | Name the host in the configSets the Host alias written into the generated configuration. |
vagrant rdp | Open a Remote Desktop sessionStarts an RDP client for the guest; normally only Windows guests support it. |
vagrant rdp -- /span | Pass arguments to the RDP clientOn Windows this runs mstsc.exe with /span, stretching the session over several desktops. |
vagrant powershell | Open a PowerShell promptStarts a remoting session from the host into a running guest; works with Windows only for now. |
vagrant powershell -c COMMAND | Run one PowerShell commandPrints the command's stdout and stderr and exits. |
vagrant powershell --elevated | Run PowerShell elevatedRaises the permissions the PowerShell command runs with; the short form is -e. |
vagrant winrm | Run commands over WinRMNeeds a guest configured with the WinRM communicator; each command is passed with --command. |
vagrant winrm -c COMMAND | Run one WinRM commandRepeat the flag to execute several commands in one call. |
vagrant winrm --shell SHELL | Pick the WinRM shellAccepts powershell or cmd; powershell is the default. |
vagrant winrm --elevated | Run WinRM commands elevatedExecutes the given commands with raised credentials. |
vagrant winrm-config | Print the WinRM configurationShows the connection settings of a guest that uses the WinRM communicator. |
Ports, uploads and synced folders 10
| Command | What it does |
|---|---|
vagrant port | List forwarded portsPrints each guest port with the host port it is mapped to. |
vagrant port NAME | List ports of one machineA multi-machine Vagrantfile requires the machine name here. |
vagrant port --guest PORT | Look up one host portPrints only the host port for that guest port, or an error if it is not forwarded; handy in scripts. |
vagrant upload SOURCE DESTINATION | Copy files to the guestSends a file or directory from the host to a destination path on the guest machine. |
vagrant upload SOURCE --temporary | Upload to a temporary locationCreates a temporary place on the guest and puts the files there. |
vagrant upload SOURCE --compress | Compress before uploadingPacks the file or directory with gzip before it is sent. |
vagrant upload SOURCE --compression-type=TYPE | Choose the compression formatTYPE is tgz or zip; zip is the default for Windows guests and tgz for all others. |
vagrant rsync | Sync rsync folders nowForces a one-off sync of rsync synced folders, which do not sync by themselves. |
vagrant rsync-auto | Sync on file changesWatches the local rsync folders and transfers on every change until you interrupt it. |
vagrant rsync-auto --[no-]poll | Toggle filesystem pollingPolling is off by default; filesystems without change events need it, at a large cost in speed. |
Boxes 29
| Command | What it does |
|---|---|
vagrant box | Manage Vagrant boxesEntry point for the subcommands add, list, outdated, prune, remove, repackage and update. |
vagrant box add NAME | Download and install a boxNAME may be a box on Vagrant Cloud, a URL, a local .box file or a catalog .json file. |
vagrant box add NAME --box-version VERSION | Add a specific box versionTakes an exact number or a constraint; without it the latest version is added. |
vagrant box add NAME --provider PROVIDER | Add a box for one providerChecks that the box being added is built for that provider. |
vagrant box add NAME --architecture ARCH | Add a box for one architectureRequires the downloaded box to match the given architecture; the short form is -a. |
vagrant box add NAME --force | Replace an installed boxDownloads again and writes over a box already present under the same name. |
vagrant box add NAME --clean | Discard a partial downloadRemoves leftovers of an earlier attempt so the transfer starts from the beginning instead of resuming. |
vagrant box add URL --name BOX | Add a box file by URLA direct box file has no catalog entry, so you supply the name; versioning and updates will not work. |
vagrant box add URL --checksum CHECKSUM --checksum-type TYPE | Verify a direct downloadVagrant compares the downloaded file with the checksum and stops with an error on a mismatch. |
vagrant box add NAME --insecure | Skip SSL verificationAn HTTPS download is accepted without checking its certificate. |
vagrant box list | List installed boxesPrints each installed box with its provider and version. |
vagrant box list --box-info | Show extra box informationAdds the details from a box's info.json file to the listing; the short form is -i. |
vagrant box outdated | Check the project's box for updatesRefreshes the box metadata to see whether it is outdated, which generally needs an internet connection. |
vagrant box outdated --global | Check all installed boxesLooks for newer versions of every box on the system, not only the one this project uses. |
vagrant box outdated --force | Ignore the cached checkBypasses the one-hour cache of the previous look-up. |
vagrant box update | Update the project's boxDownloads a newer version if one exists; a running machine keeps the old box until destroyed and recreated. |
vagrant box update --box BOX | Update a named boxWorks outside a Vagrant environment by naming the box directly. |
vagrant box update --box BOX --provider PROVIDER | Update one provider's boxOnly needed when the named box exists for more than one provider. |
vagrant box prune | Remove old box versionsPrunes outdated versions of installed boxes and asks first when one is still in use. |
vagrant box prune --dry-run | Preview what prune removesLists the candidates for removal and leaves every box in place. |
vagrant box prune --name NAME | Prune one box onlyRestricts the clean-up to old versions of the named box. |
vagrant box prune --force | Prune without confirmationRemoves old versions even while an environment is using them. |
vagrant box prune --force --keep-active-boxes | Prune but keep boxes in useSkips the prompt yet leaves alone any version an environment still depends on. |
vagrant box remove NAME | Remove a boxDeletes the installed box with that name from Vagrant. |
vagrant box remove NAME --box-version VERSION | Remove one box versionNeeded when several versions are installed; accepts a version or a constraint. |
vagrant box remove NAME --all | Remove all versions of a boxClears every installed version in one go instead of naming each. |
vagrant box remove NAME --provider PROVIDER | Remove one provider's boxRequired when the box is installed for several providers; with a single provider Vagrant picks it. |
vagrant box remove NAME --force | Remove a box that is in useDeletes it without asking, even if an active environment still depends on it. |
vagrant box repackage NAME PROVIDER VERSION | Rebuild a .box fileWrites that version of the installed box back to a .box file in the current directory for redistribution. |
Snapshots 12
Do not mix push and pop with save and restore on the same machine; the documentation calls that unsafe.
| Command | What it does |
|---|---|
vagrant snapshot | Manage snapshotsEntry point for push, pop, save, restore, list and delete; not every provider supports snapshots. |
vagrant snapshot push | Push a snapshotTakes an unnamed snapshot and puts it on the snapshot stack. |
vagrant snapshot pop | Restore the pushed snapshotReturns the machine to the last pushed state and then deletes that snapshot. |
vagrant snapshot pop --no-delete | Pop and keep the snapshotLets you return to the same point again later. |
vagrant snapshot pop --no-start | Pop without starting the guestLeaves the machine stopped once the state has been put back. |
vagrant snapshot save NAME | Save a named snapshotWithout a machine name it snapshots the whole environment under that one name. |
vagrant snapshot save VM-NAME NAME | Snapshot one machineLimits the named snapshot to a single machine of the environment. |
vagrant snapshot save NAME --force | Replace an existing snapshotOverwrites a snapshot of the same name without asking first. |
vagrant snapshot restore NAME | Restore a named snapshotBrings the machine back to the state stored earlier by snapshot save. |
vagrant snapshot restore NAME --no-start | Restore without startingThe guest stays powered off after the saved state is applied. |
vagrant snapshot list | List snapshotsShows every snapshot taken for the machine. |
vagrant snapshot delete NAME | Delete a snapshotSome providers, VirtualBox among them, need child snapshots deleted first, newest to oldest. |
Plugins 16
| Command | What it does |
|---|---|
vagrant plugin | Manage pluginsEntry point for install, list, update, uninstall, repair, expunge and license. |
vagrant plugin install NAME | Install a pluginNAME is a gem fetched from a remote repository, usually RubyGems, or the path of a local gem file. |
vagrant plugin install NAME --plugin-version PLUGIN_VERSION | Install a specific plugin versionAccepts an exact version or a quoted constraint such as "> 1.0.2". |
vagrant plugin install NAME --plugin-source PLUGIN_SOURCE | Add a plugin sourceNames another gem repository to fetch from; it stays in effect for later plugin installs too. |
vagrant plugin install NAME --plugin-clean-sources | Clear the default plugin sourcesRemoves every source set up so far, defaults included; meant for corporate firewalls that block RubyGems.org. |
vagrant plugin install NAME --local | Install for this project onlyKeeps the plugin inside the current Vagrant project instead of installing it globally. |
vagrant plugin list | List installed pluginsShows each plugin with its version and any version constraint set at install time. |
vagrant plugin list --local | Include project pluginsAdds plugins installed for the current project to the listing. |
vagrant plugin update | Update all pluginsRespects the version constraints given when each plugin was installed. |
vagrant plugin update NAME | Update one pluginLeaves the others alone and does not install the plugin if it is missing. |
vagrant plugin uninstall NAME | Uninstall a pluginAlso removes its dependencies when no other plugin needs them; several names may be given. |
vagrant plugin repair | Repair broken pluginsTries to fix plugins that fail to initialise, for example after a bad install or manual edits to plugins.json. |
vagrant plugin expunge | Remove all user pluginsDeletes every user-installed plugin gem, its dependencies and the plugins.json file. |
vagrant plugin expunge --reinstall | Expunge and reinstall pluginsWipes the plugins and then tries to install the configured ones again, useful after upgrading Vagrant. |
vagrant plugin expunge --force | Expunge without confirmationSkips the question that normally precedes removal. |
vagrant plugin license NAME LICENSE-FILE | Install a plugin licenseFor proprietary plugins such as the VMware Fusion provider. |
Status and output options 10
global-status reads a cache and does not check the machines, so an entry can say running after a host restart.
| Command | What it does |
|---|---|
vagrant status | Show machine statesTells you whether each machine in the current project is running, suspended or not created. |
vagrant global-status | List all Vagrant environmentsCovers every active environment of the logged-in user, with IDs usable from any directory. |
vagrant global-status --prune | Remove stale entriesThe list comes from a cache; this drops entries that are no longer valid and takes noticeably longer. |
vagrant COMMAND --machine-readable | Machine-readable outputReplaces terminal output with comma-separated lines of timestamp, target, type and data for scripts. |
vagrant up --debug | Print debug outputGives the same detail as setting VAGRANT_LOG to debug. |
vagrant up --debug &> vagrant.log | Save debug output to a fileOn Linux and macOS this redirects both stdout and stderr into the log file. |
vagrant COMMAND --debug-timestamp | Debug output with timestampsAdds the time to every debug log line. |
vagrant COMMAND --timestamp | Timestamp log output |
vagrant COMMAND --no-color | Disable coloured outputUseful when output goes to a log file; VAGRANT_NO_COLOR sets the same thing globally. |
vagrant COMMAND --no-tty | Use non-interactive output |
Packaging and sharing 13
Vagrant Share is a separate plugin that Vagrant system packages do not include; install it before using share or connect.
| Command | What it does |
|---|---|
vagrant package | Package a machine as a boxTurns a running VirtualBox or Hyper-V environment into a reusable box; other providers only if they support it. |
vagrant package --output NAME | Name the box fileWithout it the result is saved as package.box. |
vagrant package --base NAME | Package a plain VirtualBox VMNAME is the name or UUID of a machine created in VirtualBox itself rather than by Vagrant. |
vagrant package --include FILE,FILE | Bundle extra filesAdds the listed files to the box, where a packaged Vagrantfile can use them. |
vagrant package --vagrantfile FILE | Embed a Vagrantfile in the boxIt is read in the Vagrantfile load order when the box is used, not copied by vagrant init. |
vagrant package --info FILE | Attach an info.json fileThe JSON details appear when boxes are listed with the -i flag. |
vagrant plugin install vagrant-share | Install Vagrant ShareShare and connect come from this plugin, which Vagrant system packages do not include. |
vagrant share | Share the environmentStarts a share session and, by default, creates a public URL that routes to the machine. |
vagrant share --ssh | Share SSH accessLets someone else log in with vagrant connect --ssh; it is off by default. |
vagrant share --full | Share every portOpens all the ports it can, for the other side to reach with vagrant connect. |
vagrant share --disable-http | Share without a public URLSkips the public HTTP endpoint and shares through the other methods only. |
vagrant connect NAME | Connect to a shared environmentNAME is the share name printed by vagrant share; you get a static IP for reaching the remote machine. |
vagrant connect --ssh NAME | SSH into a shared environmentOpens an SSH session to an environment that was shared with vagrant share --ssh. |
Vagrant Cloud 13
| Command | What it does |
|---|---|
vagrant cloud | Work with Vagrant CloudEntry point for the auth, box, provider, publish, search and version subcommands. |
vagrant login | Log in (deprecated alias)Deprecated; release 2.4.9 forwards it to the cloud auth login subcommand. |
vagrant cloud auth login | Log in to Vagrant CloudOnly needed for protected boxes or Vagrant Share; everything else works without an account. |
vagrant cloud auth login --check | Check the login stateExits with status 0 when logged in and 1 when not. |
vagrant cloud auth login --token TOKEN | Log in with a tokenStores the given access token instead of asking for a username and password. |
vagrant cloud auth logout | Sign out of Vagrant CloudDoes nothing, and is not an error, when you are already logged out. |
vagrant cloud auth whoami | Show the logged-in userValidates the stored token and prints the user it belongs to. |
vagrant cloud search QUERY | Search for boxesFinds matching boxes on Vagrant Cloud; the results can be filtered, sorted and limited. |
vagrant cloud search QUERY --provider PROVIDER | Search boxes for one providerNarrows the matches to boxes built for that provider. |
vagrant cloud search QUERY --json | Search results as JSONPrints the matches as JSON instead of the normal listing; the short form is -j. |
vagrant cloud box show ORGANIZATION/BOX-NAME | Show a box's detailsReports on the newest version of the box as stored on Vagrant Cloud. |
vagrant cloud publish ORGANIZATION/BOX-NAME VERSION PROVIDER-NAME PROVIDER-FILE | Publish a boxCreates or updates the box, its version and its provider in one step instead of with separate commands. |
vagrant cloud version release ORGANIZATION/BOX-NAME VERSION | Release a box versionAsks for confirmation, then releases a version entry that already exists. |
Environment variables 20
| Command | What it does |
|---|---|
VAGRANT_CWD | Set the working directoryVagrant looks for the Vagrantfile here instead of the directory you are in; mostly used from scripts. |
VAGRANT_VAGRANTFILE | Use another Vagrantfile nameTakes a file name, not a path, for folders that hold several Vagrantfiles. |
VAGRANT_DEFAULT_PROVIDER | Set the default providerApplies to new environments only; existing ones keep the provider they were created with until destroyed. |
VAGRANT_PREFERRED_PROVIDERS | List preferred providersOne provider or a comma-delimited list, used when Vagrant picks a provider for a new environment. |
VAGRANT_HOME | Move Vagrant's home directoryGlobal state, including downloaded boxes, lives here; the default is ~/.vagrant.d. |
VAGRANT_DOTFILE_PATH | Move the .vagrant directoryChanges where VM-specific state such as the VirtualBox VM UUID is kept. |
VAGRANT_LOG | Set the log levelAccepts debug, info, warn or error; no log messages are shown unless it is set. |
VAGRANT_LOG=info vagrant up | Run with info-level loggingPrefixing the variable works on Linux and macOS; info is the level to start troubleshooting with. |
VAGRANT_NO_COLOR | Turn colour off everywhereAny value disables colorized output for all commands. |
VAGRANT_FORCE_COLOR | Force coloured outputKeeps colour on even when no TTY is detected. |
VAGRANT_NO_PARALLEL | Disable parallel operationsEverything runs one after another, for example the provisioning of several boxes. |
VAGRANT_NO_PLUGINS | Start without pluginsStops third-party plugins from loading, which helps when one makes Vagrant unstable. |
VAGRANT_CHECKPOINT_DISABLE | Disable the version checkAny non-empty value stops the occasional request that looks for a newer Vagrant. |
VAGRANT_BOX_UPDATE_CHECK_DISABLE | Disable box update checksTurns off the automatic look-up of newer box versions globally; vagrant box update still works. |
VAGRANT_SERVER_URL | Point at another box serverSets the server boxes are fetched from; the default is Vagrant Cloud. |
VAGRANT_ALIAS_FILE | Change the aliases fileCustom command aliases are read from this file instead of ~/.vagrant.d/aliases. |
VAGRANT_DEFAULT_TEMPLATE | Set the init templateApplies whenever vagrant init runs without its own --template flag. |
VAGRANT_PREFER_SYSTEM_BIN | Prefer system ssh and rsyncUses executables from the local system rather than the copies shipped inside the Vagrant installation. |
VAGRANT_INSTALL_LOCAL_PLUGINS | Install local plugins unpromptedSkips the question asked before installing plugins that the local Vagrantfile defines. |
VAGRANT_MAX_REBOOT_RETRY_DURATION | Wait longer for rebootsSeconds to wait while a guest restarts; without it the limit is 120. |
No row on this page matches that filter.
Notes
The lifecycle
vagrant init writes a starter Vagrantfile in the current directory; edit it to pick a box and a provider, then vagrant up downloads the box if needed, creates the VM and runs provisioners. vagrant ssh logs in. vagrant halt shuts the VM down cleanly and vagrant suspend saves its state to disk so vagrant resume brings it back in seconds. vagrant destroy deletes the VM and its disk; the box file stays, so the next up is fast.
Changing the machine
Edits to the Vagrantfile take effect with vagrant reload, which is halt followed by up and re-reads the configuration. Provisioners run only on first up by default; vagrant provision re-runs them on a running machine, and vagrant reload --provision does both. vagrant port lists which guest ports are forwarded to which host ports, which answers most "why can't I reach the app" questions.
The ones people forget
vagrant global-status lists every Vagrant environment on the machine, including ones in directories you have forgotten, with their IDs — and any command that takes a target machine accepts that ID, so vagrant destroy ID cleans up a VM from anywhere. The list is cached, so vagrant global-status --prune clears entries that no longer exist. vagrant box manages downloaded box images (list, update, prune), which is where the disk space goes. vagrant package turns a configured VM into a reusable box for the rest of a team.
Questions
What is the difference between halt, suspend and destroy?
halt shuts the VM down; suspend saves its memory state for a fast resume; destroy deletes the VM entirely, keeping only the box image.
My Vagrantfile change is not applied — why?
Run vagrant reload. A running machine does not re-read the Vagrantfile until it is restarted.
How do I find VMs I created in other folders?
vagrant global-status lists them all with IDs you can pass to any command that takes a target machine, such as up, halt or destroy.
How do I re-run provisioning?
vagrant provision on a running machine, or vagrant up --provision / vagrant reload --provision.
Why does Vagrant not recognise the share command?
Vagrant Share is a plugin that the system packages do not include. Install it with vagrant plugin install vagrant-share; it also requires ngrok.
Is vagrant login still the way to sign in to Vagrant Cloud?
It still works, but the 2.4.9 help marks it as deprecated and aliased to vagrant cloud auth login. Logging in is only needed for protected boxes or Vagrant Share.
Sources and checks
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant init command reference Command form, arguments and examples
- Vagrant 2.4.9 built-in help: output of "vagrant -h" and "vagrant COMMAND -h" from the official Linux release package Usage lines and option lists of every command and subcommand
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant validate command reference Command form and example
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant version command reference vagrant version and vagrant --version
- HashiCorp Developer, Vagrant v2.4.9 documentation: More Commands (non-primary subcommands) vagrant list-commands
- HashiCorp Developer, Vagrant v2.4.9 documentation: Command-Line Interface overview Help flag and shell autocompletion
33 more source pages
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant up command reference Command form, machine names and IDs
- HashiCorp Developer, Vagrant v2.4.9 documentation: Multi-Machine Machine names and regular expressions on the command line
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant halt command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant suspend command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant resume command reference Command form and the --provision flag
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant destroy command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant global-status command reference Command form, machine IDs and the cache
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant provision command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: Provisioning: basic usage The --provision and --no-provision flags of up and reload
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant reload command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant ssh command reference Command form, machine names and extra ssh arguments
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant ssh-config command reference Command form
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant rdp command reference Command form and raw arguments
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant powershell command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant winrm command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant winrm-config command reference Command form
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant port command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant upload command reference Command form and arguments
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant rsync command reference Command form
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant rsync-auto command reference Command form and polling
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant box command reference Box subcommands and their options
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant snapshot command reference Snapshot subcommands
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant plugin command reference Plugin subcommands and examples
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant status command reference Command form
- HashiCorp Developer, Vagrant v2.4.9 documentation: Debugging VAGRANT_LOG and the --debug flag
- HashiCorp Developer, Vagrant v2.4.9 documentation: Environmental Variables VAGRANT_* environment variables and the --no-color flag
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant package command reference Command form and behaviour
- HashiCorp Developer, Vagrant v2.4.9 documentation: Vagrant Share The vagrant-share plugin
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant share command reference Command form
- HashiCorp Developer, Vagrant v2.4.9 documentation: Vagrant Share: SSH sharing vagrant share --ssh and vagrant connect --ssh
- HashiCorp Developer, Vagrant v2.4.9 documentation: Vagrant Share: Vagrant Connect vagrant share --full and vagrant connect NAME
- HashiCorp Developer, Vagrant v2.4.9 documentation: Vagrant Share: HTTP sharing The public URL and --disable-http
- HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant cloud command reference Vagrant Cloud subcommands
Every row on this page was matched to a line in the documentation above on . A binding that could not be found there is not listed.
Found a wrong or missing key? Tell us and it gets checked against the source. How we verify describes the process and its limits.