Re-couple universal image to shared UBUNTU_VERSION once devcontainers/universal publishes a resolute tag
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker, dockerfile, shell
- Domain
- build-system, devops
Research direction
Inspect the universal Dockerfile and scripts/images.sh to confirm the shared UBUNTU_VERSION build arg and current temporary pin. First run docker manifest inspect mcr.microsoft.com/devcontainers/universal:resolute; done means the tag exists, the Dockerfile uses UBUNTU_VERSION, and the temporary pin comment is removed.
Written by the indexing model from the issue text.
Description
Problem Description
The universal image is built from mcr.microsoft.com/devcontainers/universal:${UBUNTU_VERSION}, which normally tracks the shared UBUNTU_VERSION single source of truth in scripts/images.sh. When migrating the images to Ubuntu 26.04 (resolute), Microsoft's devcontainers/universal image does not yet publish a resolute tag. Its latest codename tag is noble (24.04).
As a result, universal was temporarily decoupled from the shared UBUNTU_VERSION and pinned to :noble so the migration to resolute for the other images could ship without breaking the universal build.
Desired Solution
Once Microsoft publishes a resolute (26.04) tag for mcr.microsoft.com/devcontainers/universal, re-couple the universal Dockerfile to the shared UBUNTU_VERSION build arg:
ARG UBUNTU_VERSION=resolute
FROM mcr.microsoft.com/devcontainers/universal:${UBUNTU_VERSION}
and remove the temporary pin comment.
Verification
docker manifest inspect mcr.microsoft.com/devcontainers/universal:resolute
When this succeeds, the tag is available upstream.
🤖 This response was generated by Coder Agents.
- Dominant language
- Shell
- Stars
- 127
- Forks
- 51
- Avg merge
- 2h 10m
- Merged PRs (30d)
- 2
Contributor guide
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.
More from coder/images
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
tests & disclaimer Opendocs
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Deprecated Images Open
Difficulty 1/5 Under an hour Newbie friendliness 15/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·