Add tip re. typical root cause of "Exec format error" to troubleshooting.md

Signed-off-by: Michael Vorburger <mike@vorburger.ch>
This commit is contained in:
Michael Vorburger ⛑️ 2020-11-03 22:50:16 +01:00 committed by Michael Vorburger
parent 5f897d2abe
commit 99df7c9336
No known key found for this signature in database
GPG Key ID: 56FF746E772681EB
1 changed files with 6 additions and 0 deletions

View File

@ -680,3 +680,9 @@ file `/etc/systemd/system/user@.service.d/delegate.conf` with the contents:
After logging out and loggin back in, you should have permission to set CPU After logging out and loggin back in, you should have permission to set CPU
limits. limits.
### 26) `exec container process '/bin/sh': Exec format error` (or another binary than `bin/sh`)
This can happen when running a container from an image for another architecture than the one you are running on.
For example, if a remote repository only has, and thus send you, a `linux/arm64` _OS/ARCH_ but you run on `linux/amd64` (as happened in https://github.com/openMF/community-app/issues/3323 due to https://github.com/timbru31/docker-ruby-node/issues/564).