
buluma/busyboxMaintained by: the Docker Community Where to get help: the Docker Community Forums, the Docker Community Slack, or Stack Overflow
1.34.1-uclibc, 1.34-uclibc, 1-uclibc, stable-uclibc, uclibc 1.34.1-glibc, 1.34-glibc, 1-glibc, stable-glibc, glibc 1.34.1-musl, 1.34-musl, 1-musl, stable-musl, musl 1.34.1, 1.34, 1, stable, latest
Where to file issues: [***] Supported architectures: (more info) amd64, arm32v5, arm32v6, arm32v7, arm64v8, i386, mips64le, ppc64le, riscv64, s390x Published image artifact details: repo-info repo's repos/busybox/ directory (history) (image metadata, transfer size, etc) Image updates: official-images repo's library/busybox label official-images repo's library/busybox file (history) Source of this description: docs repo's busybox/ directory (history)
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
Run BusyBox shell
$ 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. Create a Dockerfile for a binary
FROM 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, see 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:uclibc
uClibc via Buildroot (statically compiled)
busybox:glibc
glibc from Debian (which is then included in the image)
busybox:musl
musl from Alpine (statically compiled)



manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务