#21 0.111 qemu: uncaught target signal 11 (Segmentation fault) - core dumped

[suddendust]

Select Topic Area

Bug

Body

I have a GA that builds a multi platform docker image:

- name: Build and push
  uses: docker/build-push-action@v6
  with:
    context: mydir
    push: true
    tags: myrepo.io/myregistry/myproject:${{ github.event_name == 'repository_dispatch' && github.event.client_payload.latest_ver || github.event.inputs.certified_version }}-multiarch
    file: Dockerfile_multiarch
    platforms: linux/amd64,linux/arm64
    provenance: false

And here's the corresponding Dockerfile:

FROM ubuntu:20.04

ENV DEBIAN_FRONTEND noninteractive

ARG TARGETARCH

# Install required packages and dependencies for RPM
RUN apt-get update && \
    apt-get install -y wget curl vim less git python3 linux-tools-common sysstat procps libjemalloc-dev gnupg && \
    rm -rf /var/lib/apt/lists/*

RUN set -e && \
    apt-get update && \
    apt-get install -y wget java-common && \
    if [ "$TARGETARCH" = "amd64" ]; then \
        wget https://corretto.aws/downloads/latest/amazon-corretto-21-x64-linux-jdk.deb && \
        dpkg --install amazon-corretto-21-x64-linux-jdk.deb && \
        rm amazon-corretto-21-x64-linux-jdk.deb && \
        ln -s /usr/lib/x86_64-linux-gnu/libjemalloc.so.2; \
    elif [ "$TARGETARCH" = "arm64" ]; then \
        wget https://corretto.aws/downloads/latest/amazon-corretto-21-aarch64-linux-jdk.deb && \
        dpkg --install amazon-corretto-21-aarch64-linux-jdk.deb && \
        rm amazon-corretto-21-aarch64-linux-jdk.deb && \
        ln -s /usr/lib/aarch64-linux-gnu/libjemalloc.so.2; \
    else \
        echo "Unsupported architecture: $TARGETARCH" && exit 1; \
    fi

ENV JAVA_HOME="/usr/lib/jvm/java-21-amazon-corretto"
ENV PATH=$JAVA_HOME/bin:$PATH

ENV LD_PRELOAD="/libjemalloc.so.2"

RUN case $TARGETARCH in \
      amd64) arch=x64; ;; \
      arm64) arch=arm64; ;; \
      *) echo "platform=$TARGETARCH un-supported, exit ..."; exit 1; ;; \
    esac \
    && mkdir -p /usr/local/lib/async-profiler \
    && curl -L https://github.com/jvm-profiling-tools/async-profiler/releases/download/v2.9/async-profiler-2.9-linux-${arch}.tar.gz | tar -xz --strip-components 1 -C /usr/local/lib/async-profiler \
    && ln -s /usr/local/lib/async-profiler/profiler.sh /usr/local/bin/async-profiler

RUN wget -O /home/myapp/etc/jmx_prometheus_javaagent/jmx_prometheus_javaagent-0.20.0.jar https://repo1.maven.org/maven2/io/prometheus/jmx/jmx_prometheus_javaagent/0.20.0/jmx_prometheus_javaagent-0.20.0.jar && \
    ln -s /home/myapp/etc/jmx_prometheus_javaagent/jmx_prometheus_javaagent-0.20.0.jar /home/myapp/etc/jmx_prometheus_javaagent/jmx_prometheus_javaagent.jar

//some sections skipped

ENTRYPOINT ["./bin/command.sh"]

This GA runs on a Github managed ARM64 runner. On running, the Build and push step fails with;

#21 [linux/amd64  4/11] RUN case amd64 in       amd64) arch=x64; ;;       arm64) arch=arm64; ;;       *) echo "platform=amd64 un-supported, exit ..."; exit 1; ;;     esac     && mkdir -p /usr/local/lib/async-profiler     && curl -L [https://github.com/jvm-profiling-tools/async-profiler/releases/download/v2.9/async-profiler-2.9-linux-${arch}.tar.gz](https://github.com/jvm-profiling-tools/async-profiler/releases/download/v2.9/async-profiler-2.9-linux-$%7Barch%7D.tar.gz) | tar -xz --strip-components 1 -C /usr/local/lib/async-profiler     && ln -s /usr/local/lib/async-profiler/profiler.sh /usr/local/bin/async-profiler
#21 0.111 qemu: uncaught target signal 11 (Segmentation fault) - core dumped

However, when I specify only platforms: linux/arm64, the build goes through. Looks like QEMU is facing an exception while trying to build the x64 image. What might be going wrong here?

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