emelie/rust-musl-builder
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
Fork of https://github.com/emk/rust-musl-builder
14 commits 1 branch 0 tags 182 KiB
Dockerfile 60.9%
Shell 39.1%
Go to file
Eric Kidd aae972390a Add an example script for use with Travis CI
2016-09-12 07:22:46 -04:00
examples Add an example script for use with Travis CI 2016-09-12 07:22:46 -04:00
cargo-config.toml Overhaul extensively and add test script 2016-04-17 07:42:09 -04:00
Dockerfile Switch from Debian to Ubuntu 16.04 to work around Rust musl link bug 2016-09-12 06:45:04 -04:00
Dockerfile.example Overhaul extensively and add test script 2016-04-17 07:42:09 -04:00
LICENSE-APACHE.txt Add licenses 2016-04-17 07:45:08 -04:00
LICENSE-MIT.txt Add licenses 2016-04-17 07:45:08 -04:00
README.md Remind myself how to release this correctly 2016-09-12 06:48:26 -04:00
sudoers Overhaul extensively and add test script 2016-04-17 07:42:09 -04:00
test-image Rename test crate, because test is no longer a valid crate name 2016-09-12 06:43:11 -04:00

README.md

rust-musl-builder: Docker container for easily building static Rust binaries

Docker Image

Do you want to compile a completely static Rust binary with no external dependencies? If so, try:

alias rust-musl-builder='docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder'
rust-musl-builder cargo build --release

This command assumes that $(pwd) is readable and writable by uid 1000, gid 1000. It will output binaries in target/x86_64-unknown-linux-musl/release. At the moment, it doesn't attempt to cache libraries between builds, so this is best reserved for making final release builds.

Deploying your Rust application

With a bit of luck, you should be able to just copy your application binary from target/x86_64-unknown-linux-musl/release, and install it directly on any reasonably modern x86_64 Linux machine. In particular, you should be able to copy your Rust application into an Alpine Linux container.

How it works

rust-musl-builder uses musl-libc, musl-gcc, and the new rustup target support. It includes static versions of several libraries:

  • The standard musl-libc libraries.
  • OpenSSL, which is needed by many Rust applications.

Adding more C libraries

If you're using Docker crates which require specific C libraries to be installed, you can create a Dockerfile based on this one, and use musl-gcc to compile the libraries you need. For example:

FROM ekidd/rust-musl-builder

RUN VERS=1.2.8 && \
    cd /home/rust/libs && \
    curl -LO http://zlib.net/zlib-$VERS.tar.gz && \
    tar xzf zlib-$VERS.tar.gz && cd zlib-$VERS && \
    CC=musl-gcc ./configure --static --prefix=/usr/local/musl && \
    make && sudo make install && \
    cd .. && rm -rf zlib-$VERS.tar.gz zlib-$VERS

This usually involves a bit of experimentation for each new library, but it seems to work well for most simple, standalone libraries.

If you need an especially common library, please feel free to submit a pull request adding it to the main Dockerfile! We'd like to support popular Rust crates out of the box.

Development notes

After modifying the image, run ./test-image to make sure that everything works.

After making changes, they must be pushed to the stable branch to build the official stable and latest images on Docker Hub. Tagged versions of Rust (such as 1.11) must be given their own branches and manually configured on Docker Hub.

License

Either the Apache 2.0 license, or the MIT license.