summaryrefslogtreecommitdiff
path: root/contrib/podmanimage
diff options
context:
space:
mode:
authorTomSweeneyRedHat <tsweeney@redhat.com>2020-09-01 11:29:57 -0400
committerTomSweeneyRedHat <tsweeney@redhat.com>2020-09-04 07:18:09 -0400
commit38f7084d355a101c2dd38954b86853588b9dd213 (patch)
treeb50e389f5fa53a2fe9a709933f64a986c101557f /contrib/podmanimage
parentfa487a65220951e84779f200f48780666b4b9209 (diff)
downloadpodman-38f7084d355a101c2dd38954b86853588b9dd213.tar.gz
podman-38f7084d355a101c2dd38954b86853588b9dd213.tar.bz2
podman-38f7084d355a101c2dd38954b86853588b9dd213.zip
[CI:DOCS] Add note on run image fuse problem - try 2
We've recently had a number of issues reported against our pre-fabricated images on quay.io and a couple of rhel repositories throwing a fuse error when run: ``` fuse: device not found, try 'modprobe fuse' first ``` The tip on modprobe fuse is not always seen by or displayed to the end user. Adding a couple of doc pointers to hopefully help. Arises from this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1867892 and several others. Replaces: 7453 where I was going crazy with whitespace and merge issues. Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
Diffstat (limited to 'contrib/podmanimage')
-rw-r--r--contrib/podmanimage/README.md5
1 files changed, 5 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.