rust
Estimated reading time: 4 minutesRust is a systems programming language focused on safety, speed, and concurrency.
GitHub repo: https://github.com/rust-lang-nursery/docker-rust
Library reference
This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at https://hub.docker.com/images/rust
Supported tags and respective Dockerfile
links
1.34.0-stretch
,1-stretch
,1.34-stretch
,stretch
,1.34.0
,1
,1.34
,latest
(1.34.0/stretch/Dockerfile)1.34.0-slim-stretch
,1-slim-stretch
,1.34-slim-stretch
,slim-stretch
,1.34.0-slim
,1-slim
,1.34-slim
,slim
(1.34.0/stretch/slim/Dockerfile)
Quick reference
-
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow -
Where to file issues:
https://github.com/rust-lang-nursery/docker-rust/issues -
Maintained by:
the Rust Project developers -
Supported architectures: (more info)
amd64
,arm32v7
,arm64v8
,i386
-
Published image artifact details:
repo-info repo’srepos/rust/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images PRs with labellibrary/rust
official-images repo’slibrary/rust
file (history) -
Source of this description:
docs repo’srust/
directory (history) -
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is Rust?
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.
How to use this image
Start a Rust instance running your app
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 rust:1.31
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
Compile your app inside the Docker container
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 rust:1.23.0 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
.
Image Variants
The rust
images come in many flavors, each designed for a specific use case.
rust:<version>
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.
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.
Some of these tags may have names like stretch in them. These are the suite code names for releases of Debian and indicate which release the image is based on.
rust:<version>-slim
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 rust
image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
License
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).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository’s rust/
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.