Running 32bit on a 64bit host with SystemCallArchitectures will fail without much information
I didn't expect this to require a real issue. It's just me trying to debug a non-starting restic-server for 1h, simply because I didn't see an amd64 build was available - github collapses the release artifacts due to the amount of attachments - and the "native" setting in the default service unit will create weird crashes.
Effectively you get 0 information, it just crashes with code=killed, status=31/SYS (which is true for anything running into filtered system calls).
What is the purpose of this change? What does it change?
Add some note about a possibly weird failure of running rest-server with the systemd unit, when trying to run the i386 binary on amd64
Was the change discussed in an issue or in the forum before?
Running 32bit on a 64bit host with SystemCallArchitectures will fail without much information
I didn't expect this to require a real issue. It's just me trying to debug a non-starting restic-server for 1h, simply because I didn't see an amd64 build was available - github collapses the release artifacts due to the amount of attachments - and the "native" setting in the default service unit will create weird crashes. Effectively you get 0 information, it just crashes with
code=killed, status=31/SYS(which is true for anything running into filtered system calls).What is the purpose of this change? What does it change?
Add some note about a possibly weird failure of running rest-server with the systemd unit, when trying to run the i386 binary on amd64
Was the change discussed in an issue or in the forum before?
No
Checklist
changelog/unreleased/that describes the changes for our users (template here)gofmton the code in all commits