Skip to content

Devcontainer: Fix missing yarn gpg key#4124

Open
jarlhengstmengel wants to merge 2 commits intodevelopfrom
devcontainer_fix_expired_gpg_key
Open

Devcontainer: Fix missing yarn gpg key#4124
jarlhengstmengel wants to merge 2 commits intodevelopfrom
devcontainer_fix_expired_gpg_key

Conversation

@jarlhengstmengel
Copy link
Copy Markdown
Contributor

Short description

This fixes missing public gpg key for yarn when building the docker image in the devcontainer. I used the solution as mentioned in the comment section of this bug report. This came up while I tried to rebuild my devcontainer in VS code.

Proposed changes

  • Curl for public gpg key for yarn and store it so that apt finds it

Side effects

  • Should be none. I'm not entirely shure if this is something that is going to be solved externally or if this is a good long term fix for us here

Faithfulness to issue description and design

There are no intended deviations from the issue and design.

How to test

Build the devcontainer in VS Code

Resolved issues

Fixes: # n.a.


Pull Request Review Guidelines

@jarlhengstmengel jarlhengstmengel added the infrastructure Issues related to the dev or production environment label Jan 30, 2026
@dkehne
Copy link
Copy Markdown
Collaborator

dkehne commented Jan 30, 2026

Since yarn is never installed via apt in this Dockerfile (Node comes through n), would it be simpler to just remove the stale source list instead?

RUN rm -f /etc/apt/sources.list.d/yarn.list

That way we don't depend on an external URL and avoid the same issue if the key expires again.

Copy link
Copy Markdown
Collaborator

@dkehne dkehne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nit: the new RUN could be folded into the next one to avoid an extra Docker layer:

RUN rm -f /etc/apt/sources.list.d/yarn.list && \
    apt-get update && \
    ...

@hannaseithe hannaseithe self-assigned this Feb 9, 2026
@hannaseithe
Copy link
Copy Markdown
Contributor

Please correct me if I am wrong: I am not entirely sure this PR is actually necessary. I am assuming the yarn.list file only exists locally on your container? Probably you added the file when installing yarn manually at some point, since the build itself doesn't create it. And if that is the case, I would expect you to do a manual rm -f /etc/apt/sources.list.d/yarn.list.

Honestly I doubt yarn is enabled and therefore used at all. @dkehne said its installed through n, which is true as it installs corepack with node (from Node.js 14.19 / 16.9) . But since we do not seem to enable corepack anywhere, yarn cant also be used.

Copy link
Copy Markdown
Contributor

@hannaseithe hannaseithe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment above

@hannaseithe hannaseithe added this to the Next milestone Mar 17, 2026
@MizukiTemma
Copy link
Copy Markdown
Member

From Weekly on 08.04: we'll review and merge this PR as it is necessary for people using dev container.

Copy link
Copy Markdown
Member

@MizukiTemma MizukiTemma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't observe any harm as user without dev container -> Approved 😸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Issues related to the dev or production environment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants