Docker Hub | GitHub Container Registry | Quay.io
Mirrors official rust
Docker images.
1-bullseye
,1.83-bullseye
,1.83.0-bullseye
,bullseye
1-slim-bullseye
,1.83-slim-bullseye
,1.83.0-slim-bullseye
,slim-bullseye
1-bookworm
,1.83-bookworm
,1.83.0-bookworm
,bookworm
,1
,1.83
,1.83.0
,latest
1-slim-bookworm
,1.83-slim-bookworm
,1.83.0-slim-bookworm
,slim-bookworm
,1-slim
,1.83-slim
,1.83.0-slim
,slim
1-alpine3.20
,1.83-alpine3.20
,1.83.0-alpine3.20
,alpine3.20
1-alpine3.21
,1.83-alpine3.21
,1.83.0-alpine3.21
,alpine3.21
,1-alpine
,1.83-alpine
,1.83.0-alpine
,alpine
beta-bullseye
,1.84.0-beta-bullseye
,1.84.0-beta.$n-bullseye
beta-bullseye-slim
,1.84.0-beta-bullseye-slim
,1.84.0-beta.$n-bullseye-slim
beta
,1.84.0-beta
,1.84.0-beta.$n
,beta-bookworm
,1.84.0-beta-bookworm
,1.84.0-beta.$n-bookworm
beta-slim
,1.84.0-beta-slim
,1.84.0-beta.$n-slim
,beta-bookworm-slim
,1.84.0-beta-bookworm-slim
,1.84.0-beta.$n-bookworm-slim
beta-alpine
,1.84.0-beta-alpine
,1.84.0-beta.$n-alpine
,beta-alpine3.21
,1.84.0-beta-alpine3.21
,1.84.0-beta.$n-alpine3.21
beta-alpine3.20
,1.84.0-beta-alpine3.20
,1.84.0-beta.$n-alpine3.20
Mirrors official rust-lang/rust:nightly
Docker images, but preserves versions for each date.
nightly
,nightly-$date
,nightly-bookworm
,nightly-bookworm-$date
nightly-slim
,nightly-slim-$date
,nightly-bookworm-slim
,nightly-bookworm-slim-$date
nightly-bullseye
,nightly-bullseye-$date
nightly-bullseye-slim
,nightly-bullseye-slim-$date
nightly-alpine
,nightly-alpine-$date
,nightly-alpine3.21
,nightly-alpine3.21-$date
nightly-alpine3.20
,nightly-alpine3.20-$date
Rust is a systems programming language sponsored by Mozilla Research. It is designed to be a "safe, concurrent, practical language", supporting functional and imperative-procedural paradigms. Rust is syntactically similar to C++, but is designed for better memory safety while maintaining performance.
The most straightforward way to use this image is to use a Rust container as both the build and runtime environment. In your Dockerfile
, writing something along the lines of the following will compile and run your project:
FROM instrumentisto/rust:beta
WORKDIR /usr/src/myapp
COPY . .
RUN cargo install --path .
CMD ["myapp"]
Then, build and run the Docker image:
$ docker build -t my-rust-app .
$ docker run -it --rm --name my-running-app my-rust-app
There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
$ docker run --rm --user "$(id -u)":"$(id -g)" -v "$PWD":/usr/src/myapp -w /usr/src/myapp instrumentisto/rust:beta cargo build --release
This will add your current directory, as a volume, to the container, set the working directory to the volume, and run the command cargo build --release
. This tells Cargo, Rust's build system, to compile the crate in myapp
and output the executable to target/release/myapp
.
The instrumentisto/rust
images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like bookworm
or bullseye
in them. These are the suite code names for releases of Debian and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
This tag is based off of buildpack-deps
. buildpack-deps
is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run rust
. Unless you are working in an environment where only the instrumentisto/rust
image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
This image is based on the popular Alpine Linux project, available in the alpine
official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as git
or bash
) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile
(see the alpine
image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
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).
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.
The sources for producing instrumentisto/rust
Docker images are licensed under Blue Oak Model License 1.0.0.
We can't notice comments/reviews in the Docker Hub so don't use them for reporting issue or asking question.
If you have any problems with or questions about this image, please contact us through a GitHub issue.