diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-09-07 09:46:43 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-07 09:46:43 -0400 |
| commit | 15375b549f5f86e773904ce4cf97fdcf1d5dcbb8 (patch) | |
| tree | 10075228fb66e40e14f0343a7b12fa210ef7d5c4 | |
| parent | abb474054c81535d2f696601646b01e3483c2fa5 (diff) | |
| parent | 38f7084d355a101c2dd38954b86853588b9dd213 (diff) | |
| download | podman-15375b549f5f86e773904ce4cf97fdcf1d5dcbb8.tar.gz podman-15375b549f5f86e773904ce4cf97fdcf1d5dcbb8.tar.bz2 podman-15375b549f5f86e773904ce4cf97fdcf1d5dcbb8.zip | |
Merge pull request #7524 from TomSweeneyRedHat/dev/tsweeney/fusemod2
[CI:DOCS] Add note on run image fuse problem - try 2
| -rw-r--r-- | contrib/podmanimage/README.md | 5 | ||||
| -rw-r--r-- | troubleshooting.md | 25 |
2 files changed, 30 insertions, 0 deletions
diff --git a/contrib/podmanimage/README.md b/contrib/podmanimage/README.md index d6abb8ae6..7641f6c7e 100644 --- a/contrib/podmanimage/README.md +++ b/contrib/podmanimage/README.md @@ -49,3 +49,8 @@ podman images exit ``` + +**Note:** If you encounter a `fuse: device not found` error when running the container image, it is likely that +the fuse kernel module has not been loaded on your host system. Use the command `modprobe fuse` to load the +module and then run the container image. To enable this automatically at boot time, you can add a configuration +file to `/etc/modules.load.d`. See `man modules-load.d` for more details. diff --git a/troubleshooting.md b/troubleshooting.md index 7e8f9bcb0..9677b1821 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -592,3 +592,28 @@ access to that port. For example: ``` $ podman run --pod srcview --name src-expose -v "${PWD}:/var/opt/localrepo":Z,ro sourcegraph/src-expose:latest serve /var/opt/localrepo ``` + +### 24) Podman container images fail with `fuse: device not found` when run + +Some container images require that the fuse kernel module is loaded in the kernel +before they will run with the fuse filesystem in play. + +#### Symptom + +When trying to run the container images found at quay.io/podman, quay.io/containers +registry.access.redhat.com/ubi8 or other locations, an error will sometimes be returned: + +``` +ERRO error unmounting /var/lib/containers/storage/overlay/30c058cdadc888177361dd14a7ed7edab441c58525b341df321f07bc11440e68/merged: invalid argument +error mounting container "1ae176ca72b3da7c70af31db7434bcf6f94b07dbc0328bc7e4e8fc9579d0dc2e": error mounting build container "1ae176ca72b3da7c70af31db7434bcf6f94b07dbc0328bc7e4e8fc9579d0dc2e": error creating overlay mount to /var/lib/containers/storage/overlay/30c058cdadc888177361dd14a7ed7edab441c58525b341df321f07bc11440e68/merged: using mount program /usr/bin/fuse-overlayfs: fuse: device not found, try 'modprobe fuse' first +fuse-overlayfs: cannot mount: No such device +: exit status 1 +ERRO exit status 1 +``` + +#### Solution + +If you encounter a `fuse: device not found` error when running the container image, it is likely that +the fuse kernel module has not been loaded on your host system. Use the command `modprobe fuse` to load the +module and then run the container image afterwards. To enable this automatically at boot time, you can add a configuration +file to `/etc/modules.load.d`. See `man modules-load.d` for more details. |