aarch64/busybox
The aarch64
organization is deprecated in favor of the more-specific arm64v8
organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64. Please adjust your usages accordingly.
Dockerfile
links** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289 IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **
** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **
This image is built from the source of the official image of the same name (busybox
). Please see that image's description for links to the relevant Dockerfile
s.
If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy
GitHub repository, which are responsible for creating the Jenkins jobs which build them.
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow
Where to file issues:
https://github.com/docker-library/busybox/issues
Maintained by:
the Docker Community
Published image artifact details:
repo-info repo's repos/busybox/
directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images PRs with label library/busybox
official-images repo's library/busybox
file (history)
Source of this description:
docs repo's busybox/
directory (history)
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
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.
$ 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 binaryFROM 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:glibc
busybox:musl
busybox:uclibc
View license information for the software contained in this image.
docker pull aarch64/busybox