Or is this it? https://hub.docker.com/r/jimmycuadra/rust/
Or is this it? https://hub.docker.com/r/jimmycuadra/rust/
Container images are great for daemons with possibly complicated dependency sets that might have conflicting version requirements with other packages and can benefit from isolation from other packages that containerization gives, but seem like a pretty heavyweight solution for just installing a compiler.
- It is common for languages to have official Docker images (Java, Ruby, Python, Go, Erlang, Haskell, Julia, etc)
- In August the install process didn't work on my Debian system, eventually got guidance for workarounds from IRC
- Our build farm is docker based, application deployment environment is docker based
- Ensures development environments are identical
- Solves the multiple compiler issue
As much as I use Docker, it'd be tough for me to call it heavyweight. In terms of resource consumption Docker is just a neat wrapper over some functionality that is built in to the kernel, there is no "vm" of any sort, which is a common misconception.
What I'm not seeing is the value of a Docker image. Rust doesn't have much in the way of runtime dependencies, which is where the value of a container generally comes in. I don't know of a platform where Docker image would work but rustup.sh would not.
Packages are of course preferable if available and up-to-date.