armhf/busybox repository overview

⁠DEPRECATED

The armhf⁠ organization is deprecated in favor of the more-specific arm32v7⁠ and arm32v6⁠ organizations, as per https://github.com/docker-library/official-images#architectures-other-than-amd64⁠. Please adjust your usages accordingly.

⁠Supported tags and respective 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 Dockerfiles.

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.

⁠Quick reference

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

⁠What is BusyBox? The Swiss Army Knife of Embedded Linux

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.

⁠How to use this image

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

⁠License

View license information⁠ for the software contained in this image.