Vagrant commands

Vagrant 2.4.9 command lines, checked against the HashiCorp CLI documentation and the built-in help of that release, grouped by task: projects, machine lifecycle, provisioning, connecting, boxes, snapshots, plugins, sharing and environment variables. Words in capitals such as NAME, ID or PROVIDER stand for your own value; vagrant up --[no-]parallel means the option has a --parallel and a --no-parallel form. Machine commands also accept an ID from vagrant global-status. Docker, push and cap commands are left out.

186 commands in 12 sections. Checked row by row against HashiCorp Developer, Vagrant v2.4.9 documentation: vagrant init command reference on . Edited by Jay.

Starting a project 16

CommandWhat it does
vagrant initCreate a VagrantfileWrites a starter Vagrantfile in the current directory unless one already exists there.
vagrant init NAMECreate a Vagrantfile for a boxThe first argument is written into the config.vm.box setting of the new file.
vagrant init NAME URLSet the box and its URLThe second argument is written into the config.vm.box_url setting of the Vagrantfile.
vagrant init --minimalSkip the instructional commentsProduces a short Vagrantfile without the explanatory comments; the short form is -m.
vagrant init --forceOverwrite an existing VagrantfileReplaces the Vagrantfile already present at the current path.
vagrant init --box-version VERSION NAMEPin the box versionPuts a version number or a constraint such as "> 0.1.5" for the box into the generated file.
vagrant init --output FILEWrite the Vagrantfile elsewhereSaves the result under the given file name; a single dash sends it to standard output instead.
vagrant init --template FILEUse a custom templateGenerates the Vagrantfile from your own ERB template.
vagrant validateCheck the VagrantfilePrints "Vagrantfile validated successfully." when the file is structured correctly.
vagrant validate --ignore-providerSkip provider settingsLeaves provider-specific configuration options out of the check.
vagrant versionShow installed and latest versionMakes a network call to look up the newest release that is available.
vagrant --versionShow the installed version onlyPrints the local version number without contacting the network.
vagrant -hList the common commandsPrints the primary subcommands with a one-line summary of each.
vagrant COMMAND -hShow help for one commandPrints that command's usage line and every flag it accepts.
vagrant list-commandsList every subcommandIncludes the ones hidden from the basic help, such as rsync and docker-exec.
vagrant autocomplete install --bash --zshInstall 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.

CommandWhat it does
vagrant upCreate and start the machinesBuilds and configures the guest machines described in the Vagrantfile.
vagrant up NAMEStart one named machineTakes a machine name from the Vagrantfile; this form only works inside the project directory.
vagrant up IDStart 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 PROVIDERChoose the providerRuns the new machine on the named provider rather than the default one.
vagrant up --[no-]parallelToggle 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-errorKeep 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-providerToggle provider auto-installControls whether Vagrant tries to install a requested provider that is missing.
vagrant haltShut the machine downVagrant tries the guest's own shutdown mechanism first and cuts power only if that fails.
vagrant halt --forcePower off immediatelySkips the graceful shutdown attempt, like unplugging the guest.
vagrant suspendSuspend the machineSaves the exact running state to disk so the guest stops using host RAM and CPU.
vagrant suspend --all-globalSuspend every running machineActs on VMs across the whole system instead of one environment; the short form is -a.
vagrant resumeResume a suspended machineContinues from the saved point instead of doing a full boot.
vagrant destroyDelete the machineStops the machine and removes everything Vagrant created for it; the downloaded box stays installed.
vagrant destroy --forceSkip the confirmation promptDeletes at once instead of asking you to confirm first.
vagrant destroy --gracefulShut down before destroyingPowers the VM off cleanly first; the short form is -g.
vagrant destroy --[no-]parallelToggle parallel destroyRemoving several machines at once needs provider support and switches on --force by itself.
vagrant destroy IDDestroy a machine from anywherePass an ID printed by global-status, such as a1b2c3, to remove a machine without changing directory.

Provisioning and reload 11

CommandWhat it does
vagrant provisionRun the provisionersWorks on a running machine, which makes it a quick way to test changes to provisioning scripts.
vagrant provision --provision-with X,Y,ZRun selected provisioners onlyTakes a comma-separated list of provisioner types or names; the rest are skipped.
vagrant up --provisionForce provisioning on upProvisioners normally run only on the first up; this runs them again.
vagrant up --no-provisionStart without provisioningBrings the machine up and leaves every provisioner out, even ones set to run always.
vagrant up --provision-with X,Y,ZStart with chosen provisionersLimits the run to the listed provisioners while the machine is brought up.
vagrant reloadRestart and re-read the VagrantfileEquivalent to a halt followed by an up; needed for Vagrantfile changes to take effect.
vagrant reload --provisionRestart and provisionReloads the configuration and also runs the provisioners, which a plain reload leaves out.
vagrant reload --no-provisionRestart without provisioningStops provisioners configured for every reload from running this time.
vagrant reload --provision-with X,Y,ZRestart with chosen provisionersAfter the restart only the listed provisioner types or names are executed.
vagrant reload --forceRestart with a hard power-offSkips the graceful shutdown during the halt half of the reload.
vagrant resume --provisionResume and provisionRuns the provisioners again after waking the machine, which resume skips by default.

Connecting to a machine 18

CommandWhat it does
vagrant sshOpen an SSH sessionLogs in to the running machine and gives you a shell; a single-machine project needs no name.
vagrant ssh NAMESSH into a named machineIn a multi-machine setup use the name that vagrant status prints, such as node1.
vagrant ssh IDSSH into a machine by IDReaches a machine of another Vagrant project with the ID that global-status lists.
vagrant ssh -c COMMANDRun one command over SSHPrints the command's output and returns to the host instead of opening a shell.
vagrant ssh --plainSSH without Vagrant's authenticationConnects in plain mode, so supplying the credentials is left to you.
vagrant ssh -- EXTRA_SSH_ARGSPass extra arguments to sshEverything after the two hyphens goes straight to the ssh executable, for example to set up a reverse tunnel.
vagrant ssh-configPrint an SSH config entryThe output can go into an SSH config file so that plain ssh reaches the machine directly.
vagrant ssh-config --host NAMEName the host in the configSets the Host alias written into the generated configuration.
vagrant rdpOpen a Remote Desktop sessionStarts an RDP client for the guest; normally only Windows guests support it.
vagrant rdp -- /spanPass arguments to the RDP clientOn Windows this runs mstsc.exe with /span, stretching the session over several desktops.
vagrant powershellOpen a PowerShell promptStarts a remoting session from the host into a running guest; works with Windows only for now.
vagrant powershell -c COMMANDRun one PowerShell commandPrints the command's stdout and stderr and exits.
vagrant powershell --elevatedRun PowerShell elevatedRaises the permissions the PowerShell command runs with; the short form is -e.
vagrant winrmRun commands over WinRMNeeds a guest configured with the WinRM communicator; each command is passed with --command.
vagrant winrm -c COMMANDRun one WinRM commandRepeat the flag to execute several commands in one call.
vagrant winrm --shell SHELLPick the WinRM shellAccepts powershell or cmd; powershell is the default.
vagrant winrm --elevatedRun WinRM commands elevatedExecutes the given commands with raised credentials.
vagrant winrm-configPrint the WinRM configurationShows the connection settings of a guest that uses the WinRM communicator.

Ports, uploads and synced folders 10

CommandWhat it does
vagrant portList forwarded portsPrints each guest port with the host port it is mapped to.
vagrant port NAMEList ports of one machineA multi-machine Vagrantfile requires the machine name here.
vagrant port --guest PORTLook 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 DESTINATIONCopy files to the guestSends a file or directory from the host to a destination path on the guest machine.
vagrant upload SOURCE --temporaryUpload to a temporary locationCreates a temporary place on the guest and puts the files there.
vagrant upload SOURCE --compressCompress before uploadingPacks the file or directory with gzip before it is sent.
vagrant upload SOURCE --compression-type=TYPEChoose the compression formatTYPE is tgz or zip; zip is the default for Windows guests and tgz for all others.
vagrant rsyncSync rsync folders nowForces a one-off sync of rsync synced folders, which do not sync by themselves.
vagrant rsync-autoSync on file changesWatches the local rsync folders and transfers on every change until you interrupt it.
vagrant rsync-auto --[no-]pollToggle filesystem pollingPolling is off by default; filesystems without change events need it, at a large cost in speed.

Boxes 29

CommandWhat it does
vagrant boxManage Vagrant boxesEntry point for the subcommands add, list, outdated, prune, remove, repackage and update.
vagrant box add NAMEDownload 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 VERSIONAdd a specific box versionTakes an exact number or a constraint; without it the latest version is added.
vagrant box add NAME --provider PROVIDERAdd a box for one providerChecks that the box being added is built for that provider.
vagrant box add NAME --architecture ARCHAdd a box for one architectureRequires the downloaded box to match the given architecture; the short form is -a.
vagrant box add NAME --forceReplace an installed boxDownloads again and writes over a box already present under the same name.
vagrant box add NAME --cleanDiscard a partial downloadRemoves leftovers of an earlier attempt so the transfer starts from the beginning instead of resuming.
vagrant box add URL --name BOXAdd 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 TYPEVerify a direct downloadVagrant compares the downloaded file with the checksum and stops with an error on a mismatch.
vagrant box add NAME --insecureSkip SSL verificationAn HTTPS download is accepted without checking its certificate.
vagrant box listList installed boxesPrints each installed box with its provider and version.
vagrant box list --box-infoShow extra box informationAdds the details from a box's info.json file to the listing; the short form is -i.
vagrant box outdatedCheck the project's box for updatesRefreshes the box metadata to see whether it is outdated, which generally needs an internet connection.
vagrant box outdated --globalCheck all installed boxesLooks for newer versions of every box on the system, not only the one this project uses.
vagrant box outdated --forceIgnore the cached checkBypasses the one-hour cache of the previous look-up.
vagrant box updateUpdate 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 BOXUpdate a named boxWorks outside a Vagrant environment by naming the box directly.
vagrant box update --box BOX --provider PROVIDERUpdate one provider's boxOnly needed when the named box exists for more than one provider.
vagrant box pruneRemove old box versionsPrunes outdated versions of installed boxes and asks first when one is still in use.
vagrant box prune --dry-runPreview what prune removesLists the candidates for removal and leaves every box in place.
vagrant box prune --name NAMEPrune one box onlyRestricts the clean-up to old versions of the named box.
vagrant box prune --forcePrune without confirmationRemoves old versions even while an environment is using them.
vagrant box prune --force --keep-active-boxesPrune but keep boxes in useSkips the prompt yet leaves alone any version an environment still depends on.
vagrant box remove NAMERemove a boxDeletes the installed box with that name from Vagrant.
vagrant box remove NAME --box-version VERSIONRemove one box versionNeeded when several versions are installed; accepts a version or a constraint.
vagrant box remove NAME --allRemove all versions of a boxClears every installed version in one go instead of naming each.
vagrant box remove NAME --provider PROVIDERRemove one provider's boxRequired when the box is installed for several providers; with a single provider Vagrant picks it.
vagrant box remove NAME --forceRemove a box that is in useDeletes it without asking, even if an active environment still depends on it.
vagrant box repackage NAME PROVIDER VERSIONRebuild 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.

CommandWhat it does
vagrant snapshotManage snapshotsEntry point for push, pop, save, restore, list and delete; not every provider supports snapshots.
vagrant snapshot pushPush a snapshotTakes an unnamed snapshot and puts it on the snapshot stack.
vagrant snapshot popRestore the pushed snapshotReturns the machine to the last pushed state and then deletes that snapshot.
vagrant snapshot pop --no-deletePop and keep the snapshotLets you return to the same point again later.
vagrant snapshot pop --no-startPop without starting the guestLeaves the machine stopped once the state has been put back.
vagrant snapshot save NAMESave a named snapshotWithout a machine name it snapshots the whole environment under that one name.
vagrant snapshot save VM-NAME NAMESnapshot one machineLimits the named snapshot to a single machine of the environment.
vagrant snapshot save NAME --forceReplace an existing snapshotOverwrites a snapshot of the same name without asking first.
vagrant snapshot restore NAMERestore a named snapshotBrings the machine back to the state stored earlier by snapshot save.
vagrant snapshot restore NAME --no-startRestore without startingThe guest stays powered off after the saved state is applied.
vagrant snapshot listList snapshotsShows every snapshot taken for the machine.
vagrant snapshot delete NAMEDelete a snapshotSome providers, VirtualBox among them, need child snapshots deleted first, newest to oldest.

Plugins 16

CommandWhat it does
vagrant pluginManage pluginsEntry point for install, list, update, uninstall, repair, expunge and license.
vagrant plugin install NAMEInstall 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_VERSIONInstall a specific plugin versionAccepts an exact version or a quoted constraint such as "> 1.0.2".
vagrant plugin install NAME --plugin-source PLUGIN_SOURCEAdd a plugin sourceNames another gem repository to fetch from; it stays in effect for later plugin installs too.
vagrant plugin install NAME --plugin-clean-sourcesClear the default plugin sourcesRemoves every source set up so far, defaults included; meant for corporate firewalls that block RubyGems.org.
vagrant plugin install NAME --localInstall for this project onlyKeeps the plugin inside the current Vagrant project instead of installing it globally.
vagrant plugin listList installed pluginsShows each plugin with its version and any version constraint set at install time.
vagrant plugin list --localInclude project pluginsAdds plugins installed for the current project to the listing.
vagrant plugin updateUpdate all pluginsRespects the version constraints given when each plugin was installed.
vagrant plugin update NAMEUpdate one pluginLeaves the others alone and does not install the plugin if it is missing.
vagrant plugin uninstall NAMEUninstall a pluginAlso removes its dependencies when no other plugin needs them; several names may be given.
vagrant plugin repairRepair broken pluginsTries to fix plugins that fail to initialise, for example after a bad install or manual edits to plugins.json.
vagrant plugin expungeRemove all user pluginsDeletes every user-installed plugin gem, its dependencies and the plugins.json file.
vagrant plugin expunge --reinstallExpunge and reinstall pluginsWipes the plugins and then tries to install the configured ones again, useful after upgrading Vagrant.
vagrant plugin expunge --forceExpunge without confirmationSkips the question that normally precedes removal.
vagrant plugin license NAME LICENSE-FILEInstall 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.

CommandWhat it does
vagrant statusShow machine statesTells you whether each machine in the current project is running, suspended or not created.
vagrant global-statusList all Vagrant environmentsCovers every active environment of the logged-in user, with IDs usable from any directory.
vagrant global-status --pruneRemove stale entriesThe list comes from a cache; this drops entries that are no longer valid and takes noticeably longer.
vagrant COMMAND --machine-readableMachine-readable outputReplaces terminal output with comma-separated lines of timestamp, target, type and data for scripts.
vagrant up --debugPrint debug outputGives the same detail as setting VAGRANT_LOG to debug.
vagrant up --debug &> vagrant.logSave debug output to a fileOn Linux and macOS this redirects both stdout and stderr into the log file.
vagrant COMMAND --debug-timestampDebug output with timestampsAdds the time to every debug log line.
vagrant COMMAND --timestampTimestamp log output
vagrant COMMAND --no-colorDisable coloured outputUseful when output goes to a log file; VAGRANT_NO_COLOR sets the same thing globally.
vagrant COMMAND --no-ttyUse 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.

CommandWhat it does
vagrant packagePackage 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 NAMEName the box fileWithout it the result is saved as package.box.
vagrant package --base NAMEPackage a plain VirtualBox VMNAME is the name or UUID of a machine created in VirtualBox itself rather than by Vagrant.
vagrant package --include FILE,FILEBundle extra filesAdds the listed files to the box, where a packaged Vagrantfile can use them.
vagrant package --vagrantfile FILEEmbed 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 FILEAttach an info.json fileThe JSON details appear when boxes are listed with the -i flag.
vagrant plugin install vagrant-shareInstall Vagrant ShareShare and connect come from this plugin, which Vagrant system packages do not include.
vagrant shareShare the environmentStarts a share session and, by default, creates a public URL that routes to the machine.
vagrant share --sshShare SSH accessLets someone else log in with vagrant connect --ssh; it is off by default.
vagrant share --fullShare every portOpens all the ports it can, for the other side to reach with vagrant connect.
vagrant share --disable-httpShare without a public URLSkips the public HTTP endpoint and shares through the other methods only.
vagrant connect NAMEConnect 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 NAMESSH into a shared environmentOpens an SSH session to an environment that was shared with vagrant share --ssh.

Vagrant Cloud 13

CommandWhat it does
vagrant cloudWork with Vagrant CloudEntry point for the auth, box, provider, publish, search and version subcommands.
vagrant loginLog in (deprecated alias)Deprecated; release 2.4.9 forwards it to the cloud auth login subcommand.
vagrant cloud auth loginLog in to Vagrant CloudOnly needed for protected boxes or Vagrant Share; everything else works without an account.
vagrant cloud auth login --checkCheck the login stateExits with status 0 when logged in and 1 when not.
vagrant cloud auth login --token TOKENLog in with a tokenStores the given access token instead of asking for a username and password.
vagrant cloud auth logoutSign out of Vagrant CloudDoes nothing, and is not an error, when you are already logged out.
vagrant cloud auth whoamiShow the logged-in userValidates the stored token and prints the user it belongs to.
vagrant cloud search QUERYSearch for boxesFinds matching boxes on Vagrant Cloud; the results can be filtered, sorted and limited.
vagrant cloud search QUERY --provider PROVIDERSearch boxes for one providerNarrows the matches to boxes built for that provider.
vagrant cloud search QUERY --jsonSearch results as JSONPrints the matches as JSON instead of the normal listing; the short form is -j.
vagrant cloud box show ORGANIZATION/BOX-NAMEShow 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-FILEPublish 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 VERSIONRelease a box versionAsks for confirmation, then releases a version entry that already exists.

Environment variables 20

CommandWhat it does
VAGRANT_CWDSet the working directoryVagrant looks for the Vagrantfile here instead of the directory you are in; mostly used from scripts.
VAGRANT_VAGRANTFILEUse another Vagrantfile nameTakes a file name, not a path, for folders that hold several Vagrantfiles.
VAGRANT_DEFAULT_PROVIDERSet the default providerApplies to new environments only; existing ones keep the provider they were created with until destroyed.
VAGRANT_PREFERRED_PROVIDERSList preferred providersOne provider or a comma-delimited list, used when Vagrant picks a provider for a new environment.
VAGRANT_HOMEMove Vagrant's home directoryGlobal state, including downloaded boxes, lives here; the default is ~/.vagrant.d.
VAGRANT_DOTFILE_PATHMove the .vagrant directoryChanges where VM-specific state such as the VirtualBox VM UUID is kept.
VAGRANT_LOGSet the log levelAccepts debug, info, warn or error; no log messages are shown unless it is set.
VAGRANT_LOG=info vagrant upRun with info-level loggingPrefixing the variable works on Linux and macOS; info is the level to start troubleshooting with.
VAGRANT_NO_COLORTurn colour off everywhereAny value disables colorized output for all commands.
VAGRANT_FORCE_COLORForce coloured outputKeeps colour on even when no TTY is detected.
VAGRANT_NO_PARALLELDisable parallel operationsEverything runs one after another, for example the provisioning of several boxes.
VAGRANT_NO_PLUGINSStart without pluginsStops third-party plugins from loading, which helps when one makes Vagrant unstable.
VAGRANT_CHECKPOINT_DISABLEDisable the version checkAny non-empty value stops the occasional request that looks for a newer Vagrant.
VAGRANT_BOX_UPDATE_CHECK_DISABLEDisable box update checksTurns off the automatic look-up of newer box versions globally; vagrant box update still works.
VAGRANT_SERVER_URLPoint at another box serverSets the server boxes are fetched from; the default is Vagrant Cloud.
VAGRANT_ALIAS_FILEChange the aliases fileCustom command aliases are read from this file instead of ~/.vagrant.d/aliases.
VAGRANT_DEFAULT_TEMPLATESet the init templateApplies whenever vagrant init runs without its own --template flag.
VAGRANT_PREFER_SYSTEM_BINPrefer system ssh and rsyncUses executables from the local system rather than the copies shipped inside the Vagrant installation.
VAGRANT_INSTALL_LOCAL_PLUGINSInstall local plugins unpromptedSkips the question asked before installing plugins that the local Vagrantfile defines.
VAGRANT_MAX_REBOOT_RETRY_DURATIONWait longer for rebootsSeconds to wait while a guest restarts; without it the limit is 120.

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

33 more source pages

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.