Automic VaultAutomic Vault

brew

Install docker-engine with Homebrew, apk, chocolatey

Pack, ship and run any application as a lightweight container (Daemon). Version 29.6.1 via Homebrew; verified 2026-06-26.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install docker-engine

local Homebrew formula metadata

Linux

Alpine Linux apkverified · 92%
sudo apk add docker-engine

Alpine Linux edge package indexes · docker-engine · source: dl-cdn.alpinelinux.org

overview

Package summary

Pack, ship and run any application as a lightweight container (Daemon)

Commands and aliases

  • docker-proxy
  • dockerd
  • dockerd-rootless-setuptool.sh
  • dockerd-rootless.sh

history

Project history and usage

Docker Engine is Docker's open-source container runtime stack: the dockerd daemon, Engine API, and the client-server machinery that builds, runs, networks, stores, and manages containers, images, volumes, and related objects.

Project history

Docker Engine began as the open-source Docker daemon and API codebase and is now built from the Moby Project. The Moby README describes Moby as an open-source project created by Docker to accelerate containerization and as a modular toolkit for assembling container-based systems, with Docker committed to using Moby as upstream for Docker products.

The Engine documentation describes Docker Engine as a client-server application with dockerd, APIs, and the Docker CLI. Over time, the daemon has been refactored toward a modular container stack that relies on related projects such as containerd, runc, and BuildKit. The Moby roadmap explicitly calls out reducing duplicated runtime code by relying more on containerd and replacing the legacy builder with BuildKit.

The release history spans from v0.1.0 in March 2013 to stable Docker Engine release lines in the 2020s. Docker 1.0 arrived in June 2014, the 1.10 line in 2016 was a major early Engine generation, and modern release notes show Engine 29.x continuing security, containerd, BuildKit, runc, rootless, storage, networking, and API work.

Adoption history

Docker Engine's adoption changed package-manager culture by making dockerd a normal server-side dependency for development machines, CI builders, and Linux hosts. The package is both an end-user tool and infrastructure substrate: Docker Desktop bundles it for local development, Linux distributions package it for servers, and many higher-level tools assume a Docker-compatible daemon or API.

Its adoption also created a dependency constellation that package maintainers track closely: Docker CLI, containerd, runc, BuildKit, RootlessKit, Compose, credential helpers, storage drivers, network/firewall integrations, and daemon configuration files all have to line up for a working install.

How it is used

Users usually interact with Docker Engine through the docker CLI, while programs call the Engine API. The daemon manages images, containers, networks, and volumes, stores daemon configuration in daemon.json on supported platforms, and persists daemon data under platform-specific data directories such as /var/lib/docker on Linux.

Common package-level usage includes installing dockerd as a service, configuring daemon.json for hosts, storage, logging, proxies, or rootless mode, and keeping Engine aligned with containerd, runc, BuildKit, and Docker CLI versions.

Why package nerds care

Docker Engine is one of the packages that reshaped modern packaging: it made container images a default build and delivery unit, made daemon/API version compatibility part of everyday developer tooling, and turned low-level Linux namespaces, cgroups, layered filesystems, registries, and OCI runtimes into routine package-manager concerns.

For package nerds, docker-engine is also a stress test for packaging policy. It ships a privileged daemon, CLI integration, rootless helpers, networking and firewall behavior, storage drivers, bundled static components, security updates, and fast-moving upstream release notes. Few packages expose as many boundaries between OS packaging, language tooling, cloud CI, and application deployment.

Timeline

  • 2013: v0.1.0 is tagged in the Docker/Moby history.
  • 2014: Docker 1.0.0 is tagged.
  • 2016: Docker 1.10.0 is tagged in the early Engine release series.
  • 2017: Docker 1.13.0 is tagged; the deprecated-features documentation records several 1.13-era deprecations and removals.
  • 2025: the Moby README notes Docker v29 deprecates the old github.com/docker/docker Go module path in favor of supported Moby modules.
  • 2026: Docker Engine 29.x release notes document ongoing security, containerd, BuildKit, runc, networking, rootless, and packaging updates.

Related projects

  • Related projects include Moby, Docker CLI, Docker Compose, Docker Desktop, containerd, runc, BuildKit, RootlessKit, Docker Hub and registries, Docker credential helpers, and Mirantis Container Runtime.

security posture

Risk level: orange

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

Risk classifier

orange risk · medium confidence · infrastructure

Why

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

Signals

  • metadata:service
  • text:container

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Formula metadata declares a service or daemon block.
  • Homebrew bottle metadata is available for 2 platform targets.
  • Installs with 4 runtime dependencies.
  • Build metadata lists 3 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Linux
/etc/docker/daemon.json
Windows
%programdata%\docker\config\daemon.json

executables

Installed executables

CommandKindExposureNote
docker-proxycliglobal executable
dockerdcliglobal executable
dockerd-rootless-setuptool.shcliglobal executable
dockerd-rootless.shcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version29.6.1
manager updated2026-06-26
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/moby/moby

install metadata

Package metadata

Package keybrew:docker-engine
Version29.6.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/docker-engine
Homepagehttps://www.docker.com/
Repositoryhttps://github.com/moby/moby
Upstream docshttps://docs.docker.com/engine
LicenseApache-2.0
Source archivehttps://github.com/moby/moby.git
Last updated2026-06-26T15:13:15Z
Pulseupdated
Dependenciescontainerd, nftables, runc, tini
Build dependenciesgo, go-md2man, pkgconf
Bottleavailable (on arm64_linux, x86_64_linux)
Homebrew post-installnot defined
Servicedeclared
CaveatsTo run dockerd as the current user, execute the following commands: brew install rootlesskit slirp4netns dockerd-rootless-setuptool.sh install NOTE: As the lifecycle of containerd is managed by dockerd, do NOT run `containerd-rootless-setuptool.sh install` before `dockerd-rootless-setuptool.sh install`. To run dockerd as the root user, use `brew services` with `sudo --preserve-env=HOME`.

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedocker-engine
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • linux
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

apk95%

docker-engine 29.5.3-r0

Docker Engine (dockerd)

https://www.docker.io/

sudo apk add docker-engine
  • License: Apache-2.0
  • Architecture: x86_64
  • Source Package: docker
  • 1 dependencies
  • 1 provides
  • normalized package name match
  • Matched by: Docker Engine
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: docker-engine from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
Chocolatey95%

docker-engine

choco install docker-engine
  • normalized package name match
  • Matched by: Docker Engine
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: docker-engine from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dnspy'

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment