aboutsummaryrefslogtreecommitdiff
path: root/troubleshooting.md
diff options
context:
space:
mode:
authorMichael Vorburger ⛑️ <mike@vorburger.ch>2020-11-03 22:50:16 +0100
committerMichael Vorburger <mike@vorburger.ch>2020-11-03 22:54:34 +0100
commit99df7c93361a4c19ea8ebf112c3353447d79befd (patch)
tree96e3d27fde239662f03ae85aae66ea2b754d56d5 /troubleshooting.md
parent5f897d2abe960f2e29dd4ae87829c3c769a4423b (diff)
downloadpodman-99df7c93361a4c19ea8ebf112c3353447d79befd.tar.gz
podman-99df7c93361a4c19ea8ebf112c3353447d79befd.tar.bz2
podman-99df7c93361a4c19ea8ebf112c3353447d79befd.zip
Add tip re. typical root cause of "Exec format error" to troubleshooting.md
Signed-off-by: Michael Vorburger <mike@vorburger.ch>
Diffstat (limited to 'troubleshooting.md')
-rw-r--r--troubleshooting.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/troubleshooting.md b/troubleshooting.md
index c42afb642..2e0abae21 100644
--- a/troubleshooting.md
+++ b/troubleshooting.md
@@ -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
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).