# Install docker-machine-driver-vultr with Homebrew

Docker Machine driver plugin for Vultr Cloud. Version 2.3.0 via Homebrew; verified 2026-07-25.

## Install

```sh
sudo av install brew:docker-machine-driver-vultr
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install docker-machine-driver-vultr
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:docker-machine-driver-vultr
- **Package manager:** Homebrew
- **Version:** 2.3.0
- **Source summary:** Docker Machine driver plugin for Vultr Cloud
- **Homepage:** <https://github.com/vultr/docker-machine-driver-vultr>
- **Repository:** <https://github.com/vultr/docker-machine-driver-vultr>
- **Last updated:** 2026-07-25T14:21:57-04:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- docker-machine-driver-vultr (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 2.3.0
## Project history and usage

Docker Machine Vultr Driver is a provider plugin that lets docker-machine, and later Rancher Machine workflows, create Docker-capable hosts on Vultr. It is a narrow but historically useful package from the period when docker-machine drivers were the standard way to turn cloud VMs into Docker hosts from a laptop or CI system.

### Project history

The Vultr README describes the package as a driver for both docker-machine and Rancher Node Driver use. It now points users toward rancher-machine, noting that docker-machine is maintained there under that successor workflow, while still documenting the older driver binary installation model.

### Adoption history

Adoption is mainly visible through its role as an official Vultr-maintained driver and its Homebrew formula. The README's Rancher Machine emphasis reflects the broader migration away from upstream Docker Machine while preserving the provider-driver interface for users who still need automatic Vultr node creation.

### How it is used

Users install docker-machine or rancher-machine, place docker-machine-driver-vultr on PATH, provide a Vultr API key, and run a create command with the vultr driver. The documented options expose Vultr-specific server type, region, plan, OS, SSH key, networking, backups, firewall, tag, and startup-data controls.

### Why package nerds care

For package people, this is a clean specimen of cloud-specific Docker Machine driver packaging: a provider API wrapped as a small CLI plugin, distributed separately from the core tool, and useful only when the matching provider and orchestration workflow are in play.

### Timeline

- Docker Machine era: The driver implements the external cloud-provider plugin model.
- Rancher Machine era: The README recommends rancher-machine for successor workflows.
- Vultr APIv4 era: The documented workflow uses Vultr APIv4 personal API keys and provider-specific options.

### Related projects

- Related projects include Docker Machine, Rancher Machine, Rancher Node Driver workflows, Vultr's API, and other Docker Machine cloud drivers.

### Sources

- <https://github.com/vultr/docker-machine-driver-vultr#readme>
- <https://github.com/rancher/machine>
- <https://gitlab.com/gitlab-org/ci-cd/docker-machine>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Combined YAML source

View the package source record on GitHub. [combined/docker-machine-driver-vultr.yml](https://github.com/mxcl/pkgdb/blob/main/combined/docker-machine-driver-vultr.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph