docker pull bash 

# Quick reference

• Maintained by:
  Tianon (of the Docker Community), with Chet's support (from Bash upstream)

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

Supported tags and respective Dockerfile links

• devel-20201103, devel
• 5.1-rc3, 5.1-rc, rc
• 5.0.18, 5.0, 5, latest
• 4.4.23, 4.4, 4
• 4.3.48, 4.3
• 4.2.53, 4.2
• 4.1.17, 4.1
• 4.0.44, 4.0
• 3.2.57, 3.2, 3
• 3.1.23, 3.1
• 3.0.22, 3.0

Quick reference (cont.)

• Where to file issues:
  https://github.com/tianon/docker-bash/issues

• Supported architectures: (more info)
  amd64, arm32v6, arm32v7, arm64v8, i386, ppc64le, s390x

• Published image artifact details:
  repo-info repo's repos/bash/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/bash
  official-images repo's library/bash file (history)

• Source of this description:
  docs repo's bash/ directory (history)

What is Bash?

Bash is the GNU Project's Bourne Again SHell, a complete implementation of the IEEE POSIX and Open Group shell specification with interactive command line editing, job control on architectures that support it, csh-like features such as history substitution and brace expansion, and a slew of other features.

tiswww.case.edu/php/chet/bash/bashtop.html

How to use this image

The primary use cases this image is targeting are testing new features of more recent Bash versions before your primary distribution updates packages and testing shell scripts against different Bash versions to ensure compatibility. There are likely other interesting use cases as well, but those are the primary two the image was initially created to solve!

Notes

There are a few main things that are important to note regarding this image:

1. Bash itself is installed at /usr/local/bin/bash, not /bin/bash, so the recommended shebang is #!/usr/bin/env bash, not #!/bin/bash (or explicitly running your script via bash /.../script.sh instead of letting the shebang invoke Bash automatically). The image does not include /bin/bash, but if it is installed via the package manager included in the image, that package will install to /bin/bash and might cause confusion (although /usr/local/bin is ahead of /bin in $PATH, so as long as plain bash or /usr/bin/env are used consistently, the image-provided Bash will be preferred).

2. Bash is the only thing included, so if your scripts rely on external tools (such as jq, for example), those will need to be added manually (via apk add --no-cache jq, for example).

Interactive shell

$ docker run -it --rm bash:4.4
bash-4.4# which bash
/usr/local/bin/bash
bash-4.4# echo $BASH_VERSION
4.4.0(1)-release

Testing scripts via bind-mount

$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro bash:4.4 bash /script.sh
...
$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro bash:3.2 bash /script.sh
...

Testing scripts via Dockerfile

FROM bash:4.4

COPY script.sh /

CMD ["bash", "/script.sh"]

Then, build and run the Docker image:

$ docker build -t my-bash-app .
...
$ docker run -it --rm --name my-running-app my-bash-app
...

License

Bash is free software, distributed under the terms of the GNU General Public License, version 3.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's bash/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.