Official Repository

Last pushed: 17 hours ago
Short Description
Busybox base image.
Full Description

Supported tags and respective Dockerfile links

Quick reference

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.

Image Variants

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





View license information for the software contained in this image.

Docker Pull Command

Comments (18)
9 months ago

Where is procedure to create program working with this image?
System, packages,compilers.
Meybe Makefile with all important information?
Simple, small program in C.

a year ago

Really handy, thanks

a year ago

How can I find the Dockerfile that was used to create the official BusyBox image?

a year ago

How can I find the Dockerfile that was used to create the official BusyBox image?

2 years ago


2 years ago


2 years ago


true is a standard unix utility which does nothing except return a success exit code. It's run there so that something other than the default busybox shell runs inside the container.

2 years ago

Very impressed, thank you!

docker run --rm busybox du -h -s /
2.6M    /
2 years ago

For the default latest tag - the version of TAR does not have decompress options. It would be great if you could update this default busybox tag to a newer version. That inlcude z decompression option(s) for the tar program. Many thanks.