Automic VaultAutomic Vault

brew

使用 Homebrew, apk, chocolatey 安装 docker-engine

查看 docker-engine 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install docker-engine

local Homebrew formula metadata

Linux

Alpine Linux apk已验证 · 92%
sudo apk add docker-engine

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

概览

软件包摘要

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

命令和别名

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

历史

项目历史与用法

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.

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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.

时间线

  • 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.

安全态势

风险级别:orange

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

风险分类器

orange 风险 · 中 置信度 · infrastructure

原因

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

信号

  • metadata:service
  • text:container

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • formula 元数据声明了服务或守护进程块。
  • Homebrew bottle 元数据适用于 2 个平台目标。
  • 安装时包含 4 个运行时依赖。
  • 构建元数据列出 3 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
docker-proxycli全局可执行文件
dockerdcli全局可执行文件
dockerd-rootless-setuptool.shcli全局可执行文件
dockerd-rootless.shcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本29.6.1
管理器更新时间2026-06-26
本地数据OK
上游not checked
检测到的最新版本未检测到

https://github.com/moby/moby

安装元数据

软件包元数据

软件包键brew:docker-engine
版本29.6.1
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/docker-engine
主页https://www.docker.com/
仓库https://github.com/moby/moby
上游文档https://docs.docker.com/engine
许可证Apache-2.0
源码归档https://github.com/moby/moby.git
最后更新2026-06-26T15:13:15Z
Pulseupdated
依赖containerd, nftables, runc, tini
构建依赖go, go-md2man, pkgconf
Bottle可用 (于 arm64_linux, x86_64_linux)
Homebrew post-install未定义
服务declared
注意事项To 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`.

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

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 依赖
  • 1 提供
  • normalized package name match
  • 匹配方式: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
  • 匹配方式: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'

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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