diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-11-04 05:49:43 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-04 05:49:43 -0500 |
| commit | dfecb48f61fb0ee32f65ce66f5a32f2d41232e41 (patch) | |
| tree | 8328411e4141f8bb1d6c80ba95514395fb84dbab | |
| parent | 0a0988e6b9568a38090de24ff18f6b773cc61627 (diff) | |
| parent | 99df7c93361a4c19ea8ebf112c3353447d79befd (diff) | |
| download | podman-dfecb48f61fb0ee32f65ce66f5a32f2d41232e41.tar.gz podman-dfecb48f61fb0ee32f65ce66f5a32f2d41232e41.tar.bz2 podman-dfecb48f61fb0ee32f65ce66f5a32f2d41232e41.zip | |
Merge pull request #8237 from vorburger/patch-1
Add tip re. typical root cause of "Exec format error" to troubleshooting.md
| -rw-r--r-- | troubleshooting.md | 6 |
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). |