
Maintained by:
https://github.com/docker-library/busybox
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile linkshttps://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest/glibc/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest/uclibc/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest/musl/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest/glibc/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest-1/glibc/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest-1/uclibc/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest-1/musl/amd64/index.json
https://github.com/docker-library/busybox/blob/c***e76f680b1ef5f713500e98921a45c/latest-1/glibc/amd64/index.json
Where to file issues:
https://github.com/docker-library/busybox/issues?q=
Supported architectures: (https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/busybox/, https://hub.docker.com/r/arm32v5/busybox/, https://hub.docker.com/r/arm32v6/busybox/, https://hub.docker.com/r/arm32v7/busybox/, https://hub.docker.com/r/arm64v8/busybox/, https://hub.docker.com/r/i386/busybox/, https://hub.docker.com/r/ppc64le/busybox/, https://hub.docker.com/r/riscv64/busybox/, https://hub.docker.com/r/s390x/busybox/
Published image artifact details:
https://github.com/docker-library/repo-info/blob/master/repos/busybox (https://github.com/docker-library/repo-info/commits/master/repos/busybox)
(image metadata, transfer size, etc)
Image updates:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fbusybox
https://github.com/docker-library/official-images/blob/master/library/busybox (https://github.com/docker-library/official-images/commits/master/library/busybox)
Source of this description:
https://github.com/docker-library/docs/tree/master/busybox (https://github.com/docker-library/docs/commits/master/busybox)
Coming in somewhere between 1 and 5 Mb in on-disk size (depending on the variant), BusyBox is a very good ingredient to craft space-efficient distributions.
BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete environment for any small or embedded system.
***.org/wiki/BusyBox
!https://raw.githubusercontent.com/docker-library/docs/cc5d5e47fd7e0c57c9b8de4c1bfb6258e0dac85d/busybox/logo.png
console$ docker run -it --rm busybox
This will drop you into an sh shell to allow you to do what you want inside a BusyBox system.
Dockerfile for a binarydockerfileFROM busybox COPY ./my-static-binary /my-static-binary CMD ["/my-static-binary"]
This Dockerfile will allow you to create a minimal image for your statically compiled binary. You will have to compile the binary in some other place like another container. For a simpler alternative that's similarly tiny but easier to extend, https://hub.docker.com/_/alpine/.
The busybox images contain BusyBox built against various "libc" variants (for a comparison of "libc" variants, Eta Labs has a very nice chart which lists many similarities and differences).
For more information about the specific particulars of the build process for each variant, see Dockerfile.builder in the same directory as each variant's Dockerfile (see links above).
busybox:glibcbusybox:uclibcbusybox:muslView license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in https://github.com/docker-library/repo-info/tree/master/repos/busybox.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。


探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务