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

"kernel does not support overlay fs" even though it does #545

Closed
TomasTomecek opened this issue Mar 25, 2018 · 3 comments
Closed

"kernel does not support overlay fs" even though it does #545

TomasTomecek opened this issue Mar 25, 2018 · 3 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@TomasTomecek
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

Description

podman fails to initialize telling me kernel does not support overlay fs: driver not supported. This is a standard Fedora 27 kernel. I presume this is related to the fact that I have XFS w/o dtype.

Steps to reproduce the issue:

  1. podman --log-level debug images

Describe the results you received:

DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: override_kernelcheck=true
ERRO[0000] Could not get runtime: kernel does not support overlay fs: driver not supported

Describe the results you expected:

The list of images is presented.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:       0.3.4
Go Version:    go1.10
OS/Arch:       linux/amd64

Output of podman info:

could not get runtime: kernel does not support overlay fs: driver not supported

Additional environment details (AWS, VirtualBox, physical, etc.):

Fedora rawhide

@TomasTomecek
Copy link
Contributor Author

TomasTomecek commented Mar 25, 2018

Now I'm even more sure it's because of dtype b/c I created a new xfs partition with dtype and it works just fine. Therefore, would it be possible to

  1. make the error message more precise?
  2. and ideally suggest the user what it should do (reformat disk, use different backend)?

WDYT?

@mheon
Copy link
Member

mheon commented Mar 25, 2018

I think we've seen this before - containers/storage was dropping specific error causes for certain things and instead giving a nonspecific driver not supported error. This was fixed in containers/storage#163, but we haven't updated to pick up that fix. Let me open a PR to grab the latest version of c/storage and fix this, so we can have it resolved in the next release.

@rhatdan
Copy link
Member

rhatdan commented Mar 26, 2018

Since this is merged, I am going to close this Issue.

@rhatdan rhatdan closed this as completed Mar 26, 2018
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants