Hi,
I’m hitting an apt-get update failure when building a Codespaces devcontainer based on the Microsoft “universal” image, which then causes Features that run apt-get update (e.g. desktop-lite) to fail during installation.
Summary
mcr.microsoft.com/devcontainers/universal:5 (Ubuntu Noble) includes a Yarn APT repo entry (https://dl.yarnpkg.com/debian). During apt-get update, APT fails with:
NO_PUBKEY 62D54FD4003F6525
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
This prevents installing Features that run apt-get update during their install scripts.
Environment
- GitHub Codespaces / devcontainers CLI
- Base image:
mcr.microsoft.com/devcontainers/universal:5
- devcontainers CLI:
0.80.3
- Host kernel (Codespaces):
linux 6.8.0-1030-azure x64
Repro steps
- Create a repo with this
.devcontainer/devcontainer.json:
{
"features": {
"ghcr.io/devcontainers/features/desktop-lite:1": {
"password": "noPassword"
}
},
"forwardPorts": [5901, 6080]
}
- Build the devcontainer (Codespaces creation or
devcontainer up).
Expected
apt-get update should succeed and the feature should install normally.
Actual
Feature installation fails during apt-get update because the Yarn repo key is missing:
Running apt-get update...
Err:1 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
...
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
ERROR: Feature "Light-weight Desktop" (ghcr.io/devcontainers/features/desktop-lite) failed to install!
Notes / workaround
If I remove/disable the Yarn APT source (anything referencing dl.yarnpkg.com/debian) prior to apt-get update, the build proceeds. However, this is hard to do cleanly in Codespaces when relying on Features (without switching to a Dockerfile/custom image).
Request
Could the universal image be updated to:
- include the correct Yarn APT signing key for the configured repo, or
- remove/disable the Yarn APT source by default (if Yarn isn’t intended to be installed via that repo), or
- switch to the current recommended Yarn repo configuration (keyring +
signed-by=) so apt-get update works out-of-the-box?
If helpful, I can provide a complete Codespaces creation log, but the snippet above is the key failure.
Thanks!
Mostafa
Hi,
I’m hitting an
apt-get updatefailure when building a Codespaces devcontainer based on the Microsoft “universal” image, which then causes Features that runapt-get update(e.g.desktop-lite) to fail during installation.Summary
mcr.microsoft.com/devcontainers/universal:5(Ubuntu Noble) includes a Yarn APT repo entry (https://dl.yarnpkg.com/debian). Duringapt-get update, APT fails with:NO_PUBKEY 62D54FD4003F6525E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.This prevents installing Features that run
apt-get updateduring their install scripts.Environment
mcr.microsoft.com/devcontainers/universal:50.80.3linux 6.8.0-1030-azure x64Repro steps
.devcontainer/devcontainer.json:{ "features": { "ghcr.io/devcontainers/features/desktop-lite:1": { "password": "noPassword" } }, "forwardPorts": [5901, 6080] }devcontainer up).Expected
apt-get updateshould succeed and the feature should install normally.Actual
Feature installation fails during
apt-get updatebecause the Yarn repo key is missing:Notes / workaround
If I remove/disable the Yarn APT source (anything referencing
dl.yarnpkg.com/debian) prior toapt-get update, the build proceeds. However, this is hard to do cleanly in Codespaces when relying on Features (without switching to a Dockerfile/custom image).Request
Could the universal image be updated to:
signed-by=) soapt-get updateworks out-of-the-box?If helpful, I can provide a complete Codespaces creation log, but the snippet above is the key failure.
Thanks!
Mostafa