Can't "apk add" on arm64/linux Alpine

[jamesarosen]

Select Topic Area

Bug

Body

Starting some time in the last few days, our GitHub Actions builds started failing. I've reduced the problem to the following workflow:

name: PR Workflow
on:
  pull_request:
jobs:
  debug-container:
    name: Build Docker Container Images
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Build image
        run: docker buildx build --platform linux/arm64 . -f ./Dockerfile

and Dockerfile:

FROM --platform=linux/arm64 node:22-alpine AS builder
RUN apk add --no-cache curl
CMD ["curl", "https://www.google.com"]

This fails reliably with

Dockerfile:2
--------------------
   1 |     FROM --platform=linux/arm64 node:22-alpine AS builder
   2 | >>> RUN apk add --no-cache curl
   3 |     CMD ["curl", "https://www.google.com/"]
   4 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c apk add --no-cache curl" did not complete successfully: exit code: 255

If I remove the --platform argument from the docker buildx build command and the FROM command, the build passes. Either is enough to trigger the error.

I tried changing the apk add to ignore TLS problems:

RUN apk add --no-cache --allow-untrusted --no-check-certificate --repository http://dl-cdn.alpinelinux.org/alpine/v3.20/main curl

The error still occurs.

[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. ⭐