# docker-machine mit Homebrew, chocolatey, MacPorts, pacman, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für docker-machine in AI-Agent-Workflows.

## Installation

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

## Antwort zur Agent-Sicherheit

docker-machine provisions and manages Docker hosts and credentials.

- **Credential-Zugriff:** Reads machine certificates, SSH keys, and Docker host credentials.
- **Änderungen an Remote-Zustand:** Can create, remove, start, stop, and configure Docker hosts.
- **Publish-/Artefakt-Risiko:** Can expose or replace infrastructure used for container workloads.
- **Empfohlene Kontrolle:** Gate create, rm, regenerate-certs, env, and host mutation commands.
- **Hinweise für Agent-Nutzung:** Allow inspect/status; require approval for host creation, deletion, and credential export.

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install docker-machine
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install docker-machine
```

  Evidenz: MacPorts ports tree: devel/docker-machine/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- pacman (92%):

```sh
sudo pacman -S docker-machine
```

  Evidenz: Arch Linux sync databases: docker-machine from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

### Windows

- Chocolatey (92%):

```sh
choco install docker-machine
```

  Evidenz: Chocolatey community package catalog: docker-machine from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dispcalgui.install'

- Scoop (92%):

```sh
scoop install main/docker-machine
```

  Evidenz: Scoop official bucket manifest trees: bucket/docker-machine.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:docker-machine
- **Paketmanager:** Homebrew
- **Version:** 0.16.2-gitlab.52
- **Quellzusammenfassung:** Create Docker hosts locally and on cloud providers
- **Homepage:** <https://docs.gitlab.com/runner/executors/docker_machine.html>
- **Zuletzt aktualisiert:** 2026-07-29T17:58:37Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- docker-machine (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.16.2-gitlab.52
## Projektgeschichte und Nutzung

Docker Machine is the CLI that automated creation of Docker hosts on local hypervisors, cloud providers, and private infrastructure. It belongs to the pre-Docker-Desktop and pre-managed-Kubernetes period of Docker tooling, when creating a VM, installing Docker Engine, and pointing the local docker client at it were routine development and CI tasks.

### Projektgeschichte

The original Docker Machine README describes a tool that creates servers, installs Docker on them, and configures the Docker client to talk to those hosts. It supported local VM drivers such as VirtualBox and cloud drivers such as DigitalOcean, with an extension model for third-party driver plugins.

The packaged Homebrew line follows GitLab's fork. GitLab states that the fork exists to fix critical bugs for the GitLab Runner Docker Machine executor after Docker deprecated Docker Machine on 2021-09-27. GitLab also states that it does not plan new features, and that maintenance is limited to critical bug fixes, CI execution reliability, and cost-impacting issues.

### Adoptionsgeschichte

Docker Machine was widely adopted because it gave the Docker CLI a repeatable way to target disposable local and cloud hosts before Docker Desktop, Docker contexts, managed container platforms, and autoscaling CI runners became the dominant workflows. Its driver-plugin model let vendors and community maintainers ship provider support outside the core binary.

The GitLab fork preserved Docker Machine for GitLab Runner's docker+machine autoscaling executor. GitLab's documentation points users toward its newer autoscaling solution, generally available from GitLab 17.1, and says the Docker Machine fork will be supported only until GitLab 20.2 in May 2027.

### Wie es verwendet wird

Typical usage is docker-machine create with a local or cloud driver, docker-machine ls to inspect hosts, docker-machine env to export Docker client environment variables, and docker-machine rm to remove a host. The tool also stores per-machine TLS material under ~/.docker/machine so the client can securely reach remote Docker daemons.

### Warum Paket-Nerds sich dafür interessieren

Docker Machine is package-nerd significant because it turned a messy cross-provider bootstrap workflow into one installable CLI plus plugin binaries. Its later life as a maintained GitLab fork is also instructive: package managers can keep legacy automation alive long after the original upstream project leaves the center of the ecosystem.

### Zeitleiste

- Docker Machine era: The upstream project standardized docker-machine create, env, ls, and driver plugins for Docker hosts.
- 2021-09-27: GitLab records Docker Machine as deprecated by Docker.
- GitLab fork era: GitLab maintains a fork for critical fixes needed by the GitLab Runner Docker Machine executor.
- GitLab 17.1: GitLab's replacement autoscaling solution is generally available.
- May 2027: GitLab plans support for its Docker Machine fork until GitLab 20.2.

### Related projects

- Related projects include Docker Engine, boot2docker, Docker Desktop, Docker contexts, GitLab Runner's docker+machine executor, Rancher Machine, and the family of Docker Machine provider drivers.

### Quellen

- <https://github.com/docker/machine#readme>
- <https://gitlab.com/gitlab-org/ci-cd/docker-machine>
- <https://docs.gitlab.com/runner/executors/docker_machine>


## Sicherheitshinweise

formula declares a Homebrew service. infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- formula declares a Homebrew service
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.docker/machine

## Credential files

- Unix: ~/.docker/machine/machines/*/*.pem
## Andere Paketmanager-Einträge

- pacman - docker-machine - 0.16.2-6: normalized package name match | Arch Linux sync databases: docker-machine from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Machine management for a container-centric world | https://github.com/docker/machine
- MacPorts - docker-machine: normalized package name match | MacPorts ports tree: devel/docker-machine/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - docker-machine: normalized package name match | Chocolatey community package catalog: docker-machine from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dispcalgui.install'
- Scoop - main/docker-machine: normalized package name match | Scoop official bucket manifest trees: bucket/docker-machine.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
- curated agent safety answer