Automated builded images for rust-lang with rustup, "the ultimate way to install RUST"

刘冲

Last update: Nov 30, 2022

Related tags

Deployment docker rust dockerfile rust-lang rustup musl

Overview

rustup

Automated builded images on store and hub for rust-lang with musl added, using rustup "the ultimate way to install RUST".

tag changed: all3 -> all

note:

Image buildings are triggered by automated builds on cloud.docker.com when "build branch" is updated by build.sh
Please check liuchong/rustup tags on store instead of Build Details on hub
The "build branch" and "tags" are meaningless but just docker images(which are with stable/versions tags) for building
the "version tags" are available from 1.15.0
the stable/beta/nightly tags does not have the package "musl-tools" and the target "x86_64-unknown-linux-musl" installed by default

Usage

Images

pull the images:

> docker pull liuchong/rustup
> docker pull liuchong/rustup:musl

the tags are:

stable/version: (stable/Dockerfile)
stable-musl/version-musl: (stable_musl/Dockerfile)
beta: (beta/Dockerfile)
beta-musl: (beta_musl/Dockerfile)
nightly: (nightly/Dockerfile)
nightly-musl: (nightly_musl/Dockerfile)
nightly-onbuild: (nightly_onbuild/Dockerfile)
nightly-musl-onbuild: (nightly_musl_onbuild/Dockerfile)
all: (all/Dockerfile)
all-musl, musl, latest: (all_musl/Dockerfile)
plus: (plus/Dockerfile)

use the image

just setup the Dockerfile:

FROM liuchong/rustup:stable
...

or you maybe prefer to make a musl static building:

# you can also use "latest", which is the same as "musl".
docker run -v $PWD:/build_dir -w /build_dir -t liuchong/rustup:musl cargo build --release
# or, you may want to use nightly channel and fix the ownership and remove container after run as below:
docker run --rm -v $PWD:/build_dir -w /build_dir -t liuchong/rustup:musl sh -c "rustup run nightly cargo build --release && chown -R $(id -u):$(id -g) target"

then, you can write a dockerfile like this and build you app image(so, the image will be very small):

FROM scratch
ADD target/x86_64-unknown-linux-musl/release/your-app /
CMD ["/your-app"]
# or something like this:
# CMD ["/your-app", "--production"]

Build script

# Use automatical checked version from website for current stable builds:
./build.sh
# Use a specified stable version from command line:
./build.sh 1.21.0
# Do not build versioning tag, just pass a string which is not fit the version pattern,
# as the first argument:
./build.sh no-version
./build.sh foo

License

MIT

Comments

Can't update toolchains

I tried to build a docker image based on your rustup images (thank you so much for these, by the way), and wanted to update the nightly toolchain to the one that's currently out, using this naive method:

rustup update nightly

Sadly, this runs into the following problem in docker:

unable to update due to layerfs

Step 3/4 : RUN rustup update nightly

 ---> Running in 8b72657bbc0c

[91minfo: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
[0m
[91minfo: latest update on 2017-09-16, rust version 1.22.0-nightly (fd4bef54a 2017-09-15)
[0m
[91minfo: downloading component 'rustc'
[0m
[91minfo: downloading component 'rust-std'
[0m
[91minfo: downloading component 'cargo'
[0m
[91minfo: downloading component 'rust-docs'
[0m
[91minfo: removing component 'rustc'
[0m
[91minfo: removing component 'rust-std'
[0m
[91minfo: removing component 'cargo'
[0m
[91minfo: removing component 'rust-docs'
[0m
[91minfo: rolling back changes
[0m
[91merror: could not rename component directory from '/root/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/share/doc/rust/html' to '/root/.rustup/tmp/omziwl1d4tvp_f9p_dir/bk'
info: caused by: Invalid cross-device link (os error 18)
[0m
Removing intermediate container 8b72657bbc0c

The command '/bin/sh -c rustup update nightly' returned a non-zero code: 1

(You can also see the build output on docker hub here: https://hub.docker.com/r/antifuchs/rustup-ci/builds/bh6g3fkmuykk32sav82vqlu/)

I wonder if there's something that these docker images could work around, so I'm reporting this here; it might just be unsolvable & I might have to remove the nightly toolchain and tmp dir before attempting the update.

Anyway, if you know of a solution that might work, I'd love to hear about it!

enhancement question

opened by antifuchs 2

Upgrade to newer version of binutils for nightly + musl

As mentioned in rust-lang/rust#34978, the Rust-provided MUSL components are now being built with a newer version of binutils, one that is incompatible with the version provided in the current container. The current solution is to upgrade binutils in some fashion. For Ubuntu-based containers, upgrading to 16.04 contains the fixes. I'm not sure what version of Debian will include them.

An example of output where the versions mismatch.

Thanks for all your hard work!

opened by shepmaster 2

MUSL libraries are only installed for the default toolchain, not others (like nightly)

For example:

docker run -it --rm -v my-code:/code --workdir /code liuchong/rustup:musl \
  rustup run nightly cargo build --target=x86_64-unknown-linux-musl --release

As a workaround, I am doing

rustup default nightly
rustup target add x86_64-unknown-linux-musl
cargo build --target=x86_64-unknown-linux-musl --release

opened by shepmaster 2

Add license scan report and status
Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

CircleCI

TravisCI

Jenkins

Other
opened by fossabot 1
[Non-Repo Related] Rust Crate

Hello @liuchong :) I am sorry for posting this here, but I did not know where to contact you otherwise. I am about to write a crate that I want to publish under the name "data". You are the current owner on https://crates.io for a crate with this name; but there is no activity for almost four years now.

I was wondering whether you are willing to provide ownership over the crate (name) to me, because currently, the crate is just unmaintained, the corresponding repository does not seem to exist anymore and I'd like to provide a crate with this name :) Is that possible?

opened by georglauterbach 0

Owner

刘冲

学而时习之，不亦悦乎？

GitHub https://store.docker.com/community/images/liuchong/rustup/

Docker images for compiling static Rust binaries using musl-libc and musl-gcc, with static versions of useful C libraries. Supports openssl and diesel crates.

rust-musl-builder: Docker container for easily building static Rust binaries Source on GitHub Changelog UPDATED: Major updates in this release which m