Open Dav1dde opened 2 months ago
The docs also mention downloading the binary directly from the GitHub Releases as another option besides the Docker images. I'm using this URL in for example a Ansible playbook to deploy Relay to my fleets.
getsentry/sentry
: ./install.sh
:
▶ Ensuring Relay credentials ...
relay/config.yml already exists, skipped creation.
relay Pulling
relay Pulled
Network sentry_default Creating
Network sentry_default Created
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
docker exec -it sentry-relay-run-df6adc48fb20 /bin/bash
:
root@bb87089ce332:/# /bin/relay
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
Segmentation fault (core dumped)
root@bb87089ce332:/# /bin/relay
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
Segmentation fault (core dumped)
root@bb87089ce332:/# /bin/relay
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
Segmentation fault (core dumped)
root@bb87089ce332:/#
Should I create a new issue?
Should I create a new issue?
Yes.
qemu-x86_64-static
Don't run Relay emulated.
Now that we have ARM docker images, Releases should also build ARM binaries.
We do have people directly consuming/using the released binaries from the job but not the docker images (for example @stayallive).
We should employ the same tech and build these binaries the same way we do build the docker images.