Menu
I thought I understood Docker. I understood it as a way to package up software with lots of dependencies..to basically create a little world where absolutely everything is taken care of for a piece of software. Then I stumbled upon this on DockerHub
https://hub.docker.com/_/busybox/
It's an image for BusyBox, which is a tiny little Linux binary that is meant for embedded systems. Then the top comment says:
Busybox is awesome :) By far the most useful container per byte on the entire registry.
But I don't understand at all why this image exists, which makes me think that I don't actually understand why Docker exists. What is the point of a BusyBox docker image?
276
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.
Alpine Linux is a small, security-oriented, lightweight Linux distribution based on the musl libc library and BusyBox utilities platform instead of GNU.
The docker push command takes the name of the image. It will know where to push our Docker image by looking at the image name because the name contains the registry location.
A Busybox docker image is useful if one is building a container for which busybox can fulfill its dependency chain without needing a full Linux distro.
Often, an embedded appliance can consist of nothing but a statically-linked copy of busybox, an init script that mounts procfs, sysfs, &c. with busybox-provided tools, and then the actual application being invoked. With docker setting up the filesystem namespace, even that init script isn't necessarily needed.
73
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
