Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[podman] overlay is not supported over overlayfs #3666

Closed
FrankNatoli opened this issue Dec 8, 2021 · 7 comments
Closed

[podman] overlay is not supported over overlayfs #3666

FrankNatoli opened this issue Dec 8, 2021 · 7 comments

Comments

@FrankNatoli
Copy link

FrankNatoli commented Dec 8, 2021

Have x64 Windows VirtualBox running CentOS8.
CentOS8 has no problem using docker or podman.
Containers created for CentOS8 until a few weeks ago had no problem using docker or podman.
Had GitLab crash, regenerate container, and now container image reports podman not available.
Revise Dockerfile to yum install podman in container.
Container image now can run "podman --help" but "podman ps" and "podman info" both report:
"overlay is not supported over overlayfs, a mount program is required; backing file system is unsupported for this graph driver"
This link has apparently relevant suggestions:
https://docs.docker.com/storage/storagedriver/overlayfs-driver/
However, "podman info" on CentOS8 shows no "Storage Driver:" though it does show a "graphStatus" with an xfs Backing Filesystem.
I repeat, podman runs just fine on CentOS8, despite having no "Storage Driver:" but will not run "podman ps" or "podman info" insider container.
I believe something has changed but not sure what.
Help appreciated.

@rhatdan
Copy link
Member

rhatdan commented Dec 8, 2021

The issue is /var/lib/containers within the container is not on an overlay and no longer using fuse-overlayfs because of native overlay support. You could volume mount into the container /var/lib/containers which would fix the problem, or you could force fuse-overlayfs into the container.

Did this happen when you updated to RHEL8.5?

@FrankNatoli
Copy link
Author

I am not aware of an intentional update to RHEL8.5.
We had a GitLab crash, and when I regenerated the containers, this problem appeared out of nowhere.
Have just checked.
Inside the container, /var/lib/containers has sub-directories sigstore and storage.
Outside the container, /var/lib/containers has sub-directories sigstore, storage and cache.
"podman info" inside the container reports the overlay complaint.
"podman info" outside the container displays all the info.
Are you suggesting a "-v /var/lib/containers:/var/lib/containers" for the container "podman run" command?
Thanks for your time.

@rhatdan
Copy link
Member

rhatdan commented Dec 9, 2021

I am suggesting -v ANYCONTAINERDIRNOTONOVERLAY:/var/lib/containers:Z
You can do -v /var/lib/containers:/var/lib/containers but will need to disable SELinux if you are using it.

@FrankNatoli
Copy link
Author

@rhatdan: sorry for delayed response, but your "-v /var/lib/containers:/var/lib/containers" resolved my problem, many thanks.

@oappicgi
Copy link

ide the container, /var/lib/containers has sub-directories sigstore and storage.
Outside the container, /var/lib/containers has sub-directories sigstore, storage and cache.
"podman info" inside the container reports the overlay complaint.

Thanks, "podman -v /var/lib/containers:/var/lib/containers" indeed removed the issue for me in linux mint 20.3

@w7089
Copy link

w7089 commented Dec 13, 2022

had the same issue in alpine container where I installed podman. What resolved this is adding below 2 lines to Dockerfile:

RUN apk add --no-cache --update  fuse-overlayfs
RUN sed -i 's/#mount_program/mount_program/' /etc/containers/storage.conf

@rhatdan
Copy link
Member

rhatdan commented Dec 14, 2022

You could also just add a volume /var/lib/containers to your Containerfile

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants