openeuler/busybox repository overview

⁠Quick reference

• The official BusyBox docker image.

• Maintained by: openEuler CloudNative SIG⁠.

• Where to get help: openEuler CloudNative SIG⁠, openEuler⁠.

⁠BusyBox | openEuler

Current BiSheng BusyBox images are built on the openEuler⁠. This repository is free to use and exempted from per-user rate limits.

BusyBox⁠ is a multi-call binary. A multi-call binary is an executable program that performs the same job as more than one utility program. That means there is just a single BusyBox binary, but that single binary acts like a large number of utilities. This allows BusyBox to be smaller since all the built-in utility programs (we call them applets) can share code for many common operations.

⁠Supported tags and respective Dockerfile links

The tag of each BusyBox docker image is consist of the version of BusyBox and the version of basic image. The details are as follows

⁠Usage

You can also invoke BusyBox by issuing a command as an argument on the command line. For example, entering

busybox ls

will also cause BusyBox to behave as 'ls'.

Of course, adding '/bin/busybox' into every command would be painful. So most people will invoke BusyBox using links to the BusyBox binary.

ln -s /usr/local/busybox/bin/busybox ls
./ls

will cause BusyBox to behave as 'ls' (if the 'ls' command has been compiled into BusyBox). Generally speaking, you should never need to make all these links yourself, as the BusyBox build system will do this for you when you run the 'make install' command. If you invoke BusyBox with no arguments, it will provide you with a list of the applets that have been compiled into your BusyBox binary.

⁠Question and answering

If you have any questions or want to use some special features, please submit an issue or a pull request on openeuler-docker-images⁠.