Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider publishing a 1.85 Debian Trixie container

Open
#263 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
debian, docker, rust

Research direction

Start by inspecting the repository's configuration for the existing 1.85 Docker image variants, then compare the Bookworm and Bullseye tags with the requested rust:1.85.0-slim-trixie variant. Done means a 1.85 Trixie-based image is published and available alongside the current Debian-based images.

Written by the indexing model from the issue text.

Description

Currently all the 1.85 images (https://hub.docker.com/_/rust/tags?name=1.85) are based on either Debian Bookworm or Bullseye.

Debian Trixie (stable release for approx the next 2 years) ships with 1.85 (https://packages.debian.org/source/stable/rustc, https://tracker.debian.org/pkg/rustc).

It would be useful to have Trixie based 1.85 container images available (eg, rust:1.85.0-slim-trixie) to match what Debian Stable ships with.

Dominant language
Dockerfile
Stars
537
Forks
111
Avg merge
1d 39m
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/docker-rust

All issues in rust-lang/docker-rust

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.