rust-lang / rust-lang/docker-rust
Reconsider including rustfmt and clippy in docker image
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 537
- Forks
- 111
- Avg merge
- 1d 38m
- Merged PRs (30d)
- 4
Description
The docker image has a different use case than normal installations, mostly CI. And having rustfmt and clippy available by default would greatly ease their use in CI by having the necessary tools preinstalled and not requiring a network connection to install them for each CI job.
#37 was closed by reasoning that this is the responsible of rustup, but they closed it as responsible from docker-rust: https://github.com/rust-lang/rustup/issues/1569#issuecomment-587753207. So I think it is time to reconsider including it in this repository again.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's Docker image definitions and compare the current setup with the reasoning in issue #37 and its linked rustup discussion. Confirm which images should include rustfmt and clippy, then verify that CI users can access both tools without a network install.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100