FIX MS Package Signing Key issue #1353 to enable DevContainers after Feb-01-2026#1356
FIX MS Package Signing Key issue #1353 to enable DevContainers after Feb-01-2026#1356romanlutz merged 5 commits intoAzure:mainfrom
Conversation
romanlutz
left a comment
There was a problem hiding this comment.
Does it succeed for you with these changes?
Before merging, I definitely want one of the maintainers to try this as well. I don't have objections with the changes themselves, but we should be sure that it works.
|
Thanks for reviewing! I agree - it would be great to have a maintainer verify this works in their environment as well. For context: I successfully built and opened the dev container with these changes on my machine (macOS 13.0.1, Docker Desktop 3.5.2, VS Code 1.109.0-insider). Happy to provide any additional testing information or logs if needed. Let me know if there's anything else I should add to help with verification |
@nmolivo please read and decide whether you want to accept the CLA. Otherwise, we won't be able to accept the contribution. |
|
@microsoft-github-policy-service agree |
Fixes #1353: Bug Report: Dev Container Build Fails Due to Microsoft Package Signing Key Issue
Root Cause:
The Microsoft package repository signing key uses SHA1 hashing, which Debian/APT now considers insecure as of February 1, 2026. The security policy has been tightened, causing the signature to be rejected.
Changes (minimal, transparent):
In
.devcontainer/Dockerfile