github.com/hanks177/podman/v4@v4.1.3-0.20220613032544-16d90015bc83/contrib/podmanimage/README.md (about) 1  2 3 # podmanimage 4 5 ## Overview 6 7 This directory contains the Containerfiles necessary to create the podmanimage container 8 images that are housed on quay.io under the Podman account. All repositories where 9 the images live are public and can be pulled without credentials. These container images are secured and the 10 resulting containers can run safely with privileges within the container. 11 12 The container images are built using the latest Fedora and then Podman is installed into them. 13 The PATH in the container images is set to the default PATH provided by Fedora. Also, the 14 ENTRYPOINT and the WORKDIR variables are not set within these container images, as such they 15 default to `/`. 16 17 The container images are: 18 19 * `quay.io/containers/podman:<version>` and `quay.io/podman/stable:<version>` - 20 These images are built daily. They are intended to contain an unchanging 21 and stable version of podman. For the most recent `<version>` tags (`vX`, 22 `vX.Y`, and `vX.Y.Z`) the image contents will be updated daily to incorporate 23 (especially) security upgrades. For build details, please [see the 24 configuration file](stable/Containerfile). 25 * `quay.io/containers/podman:latest` and `quay.io/podman/stable:latest` - 26 Built daily using the same Containerfile as above. The Podman version 27 will remain the "latest" available in Fedora, however the other image 28 contents may vary compared to the version-tagged images. 29 * `quay.io/podman/testing:latest` - This image is built daily, using the 30 latest version of Podman that was in the Fedora `updates-testing` repository. 31 The image is Built with [the testing Containerfile](testing/Containerfile). 32 * `quay.io/podman/upstream:latest` - This image is built daily using the latest 33 code found in this GitHub repository. Due to the image changing frequently, 34 it's not guaranteed to be stable or even executable. The image is built with 35 [the upstream Containerfile](upstream/Containerfile). 36 37 ## Sample Usage 38 39 40 ``` 41 podman pull docker://quay.io/podman/stable:latest 42 43 podman run --privileged stable podman version 44 45 # Create a directory on the host to mount the container's 46 # /var/lib/container directory to so containers can be 47 # run within the container. 48 mkdir /var/lib/mycontainer 49 50 # Run the image detached using the host's network in a container name 51 # podmanctr, turn off label and seccomp confinement in the container 52 # and then do a little shell hackery to keep the container up and running. 53 podman run --detach --name=podmanctr --net=host --security-opt label=disable --security-opt seccomp=unconfined --device /dev/fuse:rw -v /var/lib/mycontainer:/var/lib/containers:Z --privileged stable sh -c 'while true ;do sleep 100000 ; done' 54 55 podman exec -it podmanctr /bin/sh 56 57 # Now inside of the container 58 59 podman pull alpine 60 61 podman images 62 63 exit 64 ``` 65 66 **Note:** If you encounter a `fuse: device not found` error when running the container image, it is likely that 67 the fuse kernel module has not been loaded on your host system. Use the command `modprobe fuse` to load the 68 module and then run the container image. To enable this automatically at boot time, you can add a configuration 69 file to `/etc/modules.load.d`. See `man modules-load.d` for more details. 70 71 ### Blog Post with Details 72 73 Dan Walsh wrote a blog post on the [Enable Sysadmin](https://www.redhat.com/sysadmin/) site titled [How to use Podman inside of a container](https://www.redhat.com/sysadmin/podman-inside-container). In it, he details how to use these images as a rootful and as a rootless user. Please refer to this blog for more detailed information.