starred/fake-gcs-server

Fork 0

mirror of https://github.com/fsouza/fake-gcs-server.git synced 2026-04-26 06:05:54 +03:00

[GH-ISSUE #580] qemu segmentation fault on Apple M1 / arm64 #104

New issue

Closed

opened 2026-03-03 12:08:19 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 12:08:19 +03:00

Owner

Originally created by @markerdmann on GitHub (Sep 23, 2021).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/580

The container crashes immediately after startup on an M1 Macbook. This is the log output:

fakegcs_1 | time="2021-09-23T18:41:16Z" level=info msg="server started at https://[::]:4443"
fakegcs_1 | qemu: uncaught target signal 11 (Segmentation fault) - core dumped

Originally created by @markerdmann on GitHub (Sep 23, 2021). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/580 The container crashes immediately after startup on an M1 Macbook. This is the log output: fakegcs_1 | time="2021-09-23T18:41:16Z" level=info msg="server started at https://[::]:4443" fakegcs_1 | qemu: uncaught target signal 11 (Segmentation fault) - core dumped

kerem

2026-03-03 12:08:19 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@fsouza commented on GitHub (Sep 23, 2021):

@markerdmann thanks for reporting. I don't have an M1 currently, so hard for me to investigate this 😞

Are you able to reproduce it when running natively, without a container?

@fsouza commented on GitHub (Sep 23, 2021): @markerdmann thanks for reporting. I don't have an M1 currently, so hard for me to investigate this 😞 Are you able to reproduce it when running natively, without a container?

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@markerdmann commented on GitHub (Sep 23, 2021):

My current workaround is just to clone this repo and run with the fake-gcs-server/Dockerfile.

This might be the solution? https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/

@markerdmann commented on GitHub (Sep 23, 2021): My current workaround is just to clone this repo and run with the fake-gcs-server/Dockerfile. This might be the solution? https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@fsouza commented on GitHub (Sep 23, 2021):

Oh I see, is the problem only when you pull the image from Docker Hub? I'll investigate more later.

@fsouza commented on GitHub (Sep 23, 2021): Oh I see, is the problem only when you pull the image from Docker Hub? I'll investigate more later.

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@markerdmann commented on GitHub (Sep 23, 2021):

Yes, I think when building locally, Docker is able to use the multiarch builds of the two base images referenced in the Dockerfile.

@markerdmann commented on GitHub (Sep 23, 2021): Yes, I think when building locally, Docker is able to use the multiarch builds of the two base images referenced in the Dockerfile.

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@fafrd commented on GitHub (Oct 8, 2021):

Can confirm- I was able to work around this by cloning the repo and building/running the image manually:

git clone https://github.com/fsouza/fake-gcs-server.git
docker build -t fsouza/fake-gcs-server .
docker run fsouza/fake-gcs-server

in my case, I exposed the necessary ports/served on localhost for development:

docker run -p 4443:4443 fsouza/fake-gcs-server -scheme http -port 4443 -external-url http://localhost:4443

@fafrd commented on GitHub (Oct 8, 2021): Can confirm- I was able to work around this by cloning the repo and building/running the image manually: ```bash git clone https://github.com/fsouza/fake-gcs-server.git docker build -t fsouza/fake-gcs-server . docker run fsouza/fake-gcs-server ``` in my case, I exposed the necessary ports/served on localhost for development: ```bash docker run -p 4443:4443 fsouza/fake-gcs-server -scheme http -port 4443 -external-url http://localhost:4443 ```

kerem commented

2026-03-03 12:08:21 +03:00

Author

Owner

@stoffeastrom commented on GitHub (Dec 28, 2021):

@fsouza Looks like you are using github actions. There are some actions available.

https://github.com/docker/setup-buildx-action#with-qemu

Something like: (note haven't tested this myself yet)

name: docker-push
on: create

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2.4.0
        if: github.event.ref_type == 'tag'

      - uses: actions/setup-go@v2.1.5
        if: github.event.ref_type == 'tag'
        id: go
        with:
          go-version: 1.17

      - name: go-build
        if: github.event.ref_type == 'tag'
        run: go build -o fake-gcs-server
        env:
          CGO_ENABLED: 0

      - name: sanity-check
        if: github.event.ref_type == 'tag'
        uses: docker://alpine
        with:
          entrypoint: sh
          args: -c "./fake-gcs-server -h"

      - name: docker-publish
        if: github.event.ref_type == 'tag'
        uses: fsouza/docker-publish-action@v1.0.1
        with:
          dockerfile: ci/Dockerfile
          docker-image: fsouza/fake-gcs-server
          DOCKER-USERNAME: ${{ secrets.DOCKER_USERNAME }}
          docker-password: ${{ secrets.DOCKER_PASSWORD }}

      - name: setup qemu
        if: github.event.ref_type == 'tag'
        uses: docker/setup-qemu-action@v1
      - name: setup buildx
        if: github.event.ref_type == 'tag'
        id: buildx
        uses: docker/setup-buildx-action@v1
      - name: available platforms
        if: github.event.ref_type == 'tag'
        run: echo ${{ steps.buildx.outputs.platforms }}
      - name: login to docker hub
        if: github.event.ref_type == 'tag'
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_TOKEN }}
      - name: build the image
        if: github.event.ref_type == 'tag'
        run: |
          docker buildx build \
          --push \
          --tag ${{ secrets.DOCKER_USERNAME }}/fake-gcs-server:latest \
          --platform linux/amd64,linux/arm64 .

@stoffeastrom commented on GitHub (Dec 28, 2021): @fsouza Looks like you are using github actions. There are some actions available. https://github.com/docker/setup-buildx-action#with-qemu Something like: (*note* haven't tested this myself yet) ```yaml name: docker-push on: create jobs: release: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2.4.0 if: github.event.ref_type == 'tag' - uses: actions/setup-go@v2.1.5 if: github.event.ref_type == 'tag' id: go with: go-version: 1.17 - name: go-build if: github.event.ref_type == 'tag' run: go build -o fake-gcs-server env: CGO_ENABLED: 0 - name: sanity-check if: github.event.ref_type == 'tag' uses: docker://alpine with: entrypoint: sh args: -c "./fake-gcs-server -h" - name: docker-publish if: github.event.ref_type == 'tag' uses: fsouza/docker-publish-action@v1.0.1 with: dockerfile: ci/Dockerfile docker-image: fsouza/fake-gcs-server DOCKER-USERNAME: ${{ secrets.DOCKER_USERNAME }} docker-password: ${{ secrets.DOCKER_PASSWORD }} - name: setup qemu if: github.event.ref_type == 'tag' uses: docker/setup-qemu-action@v1 - name: setup buildx if: github.event.ref_type == 'tag' id: buildx uses: docker/setup-buildx-action@v1 - name: available platforms if: github.event.ref_type == 'tag' run: echo ${{ steps.buildx.outputs.platforms }} - name: login to docker hub if: github.event.ref_type == 'tag' uses: docker/login-action@v1 with: username: ${{ secrets.DOCKER_USERNAME }} password: ${{ secrets.DOCKER_TOKEN }} - name: build the image if: github.event.ref_type == 'tag' run: | docker buildx build \ --push \ --tag ${{ secrets.DOCKER_USERNAME }}/fake-gcs-server:latest \ --platform linux/amd64,linux/arm64 . ```

kerem referenced this issue

2026-03-03 12:29:34 +03:00

[PR #104] [MERGED] build(deps): bump alpine from 3.10.2 to 3.10.3 #341