Default universal image used by codespaces contains broken GPG keys

[eimhin-rover]

Select Topic Area

Bug

Body

When attempting to create a codespace from a repo containing either no devcontainer config or no base image specified in the devcontainer config, codespaces will use the mcr.microsoft.com/devcontainers/universal image. While inspecting some of the logs at creation time, I noticed it appears to pin to mcr.microsoft.com/devcontainers/universal:5.

However when you actually boot the machine and try to run sudo apt-get update the following error occurs:

13.05 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
13.05 E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.

This error stems from GPG issues associated with yarn last month which have since been dealt with in the devcontainers/images repo and released using the 5 and latest tags.
devcontainers/images#1752

Taking a deeper look into what is going on I checked the ContainerImageInfo logs on a codespace I booted and found it was actually using tag 5.0.2 rather than 5.1.4 which is the current latest release.

Can someone at Github update the default image so we don't end up with broken machines? Thanks!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐