diff options
Diffstat (limited to 'troubleshooting.md')
| -rw-r--r-- | troubleshooting.md | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index c42afb642..3ff578142 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -457,7 +457,7 @@ Attempts to run podman result in One workaround is to disable Secure Boot in your BIOS. -### 20) error creating libpod runtime: there might not be enough IDs available in the namespace +### 19) error creating libpod runtime: there might not be enough IDs available in the namespace Unable to pull images @@ -669,7 +669,7 @@ Example output might be: memory pids -In the above example, `cpu` is not listed, which means the curent user does +In the above example, `cpu` is not listed, which means the current user does not have permission to set CPU limits. If you want to enable CPU limit delegation for all users, you can create the @@ -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). |