Debian Question posted in
The oficial documentation can be found here.

Add shell or bash to a docker image (Distroless based on Debian GNU/Linux)

I want add shell or bash to my image to execute installation command.

I have copied the /bin/bash on my VM on to my image on Dockerfile:

COPY /bin/bash /bin/

But when I execute the docker command:

 docker run -it --entrypoint "/bin/bash" <my_image>

Then I get the following error :

/bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

Thanks for your help

Tags:

3

Answers


  1. 0

    That’s because you’re trying to use dynamic-compiled bash in in docker without glibc support.

    TL;DR

    • … either use bash-static instead of classic bash
      You may download it or run ./build.sh
    • or add bash for alpine: add this line to your Dockerfile: RUN apk add --no-cache bash

    Alpine is a musl-based distro

    Many docker images are built with alpine as base image:
    alpine (usually) is small & fast:

    Here are the sizes of the images of popular operating systems.

    The difference in image size
    source: A Breakdown of Operating Systems of Dockerhub

    The difference in image size is striking: the range goes from BusyBox at 1MB all the way up to Fedora at 230MB. It’s interesting to see the clustering happening. Alpine and BusyBox are lightweight and right near 0MB, then the midweights like Debian and Ubuntu are around 100MB, and largest are heavyweights such as CentOS and Oracle Linux up by 200MB.

    musl doesn’t contain libtinfo

    See more about difference between glibc and musl Functional differences from glibc

    P.S. you can run bash-static even in empty container from scratch

    FROM scratch
ADD bash
ENTRYPOINT ['/bash']

    You could probably add busybox in now.

    Login or Signup to reply.
  2. 0

    Google’s distroless images have versions tagged debug, which contain busybox executable (with sh bundled in).

    If you have to, you can arguably use them even in production (which defeats the purpose of increased security – such as hiding environment variables and protecting scripted apps code).

    Usage example of the distroless/base image with debug tag:

    $ docker run -it --rm --name base -u 0 gcr.io/distroless/base:debug
/ # id
uid=0(root) gid=0(root)
    Login or Signup to reply.
  3. 0

    You can do it by copying the statically compiled shell from official busybox image in a multi-stage build in your Dockerfile. Or just COPY --from it.

    The static shell doesn’t have so many dependencies, so it will work for a range of different base images. It may not work for some very advanced cases, but otherwise it gets the job done.

    The statically compiled shell is tagged with uclibc. Depending on your base image you may have success with other flavours of busybox as well.

    Example:

    FROM busybox:1.35.0-uclibc as busybox

FROM gcr.io/distroless/base-debian11

# Now copy the static shell into base image.
COPY --from=busybox /bin/sh /bin/sh

# You may also copy all necessary executables into distroless image.
COPY --from=busybox /bin/mkdir /bin/mkdir
COPY --from=busybox /bin/cat /bin/cat

ENTRYPOINT ["/bin/sh", "/entrypoint.sh"]

    The single-line COPY --from directly from image would also work:

    FROM gcr.io/distroless/base-debian11

COPY --from=busybox:1.35.0-uclibc /bin/sh /bin/sh

ENTRYPOINT ["/bin/sh", "/entrypoint.sh"]
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search