-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
"metacopy check" insufficient? all "sudo podman __" commands failing on ubuntu 18.04 kernel 4.15 #9363
Comments
I can confirm this bug. I noticed that my 18.04 ci job failed with
|
This change would at least make this a warning rather then a hard failure. |
@buck2202 Are you deliberately trying to run remote Podman? It looks like Podman is trying to connect remotely there, which could be another serious bug if you did not intend that. |
@mheon no, I'm not trying to run remotely. You say that because of the REST API reference in the error message? Or the "remoteSocket" section of As root, after editing storage.conf to
edit: and debug-level output of the failure with
if you're concerned about the REST reference in the error message, it only seems to appear when reporting the error. Maybe just an inapplicable string being prepended to the return from the mount test? |
@vrothberg found the issue there - looks like it was just an issue with the message displayed, which is a relief. Metacopy issue should be separate. |
I will update the containers-common package to remove |
@lsm5 not to make it too complicated, but there are 18.04 kernels that will support metacopy. The 18.04 GA kernel (original release, supported for full LTS lifetime) is 4.15, which doesn't support it. The 18.04 HWE kernel (six month rolling release) is currently up to (I think) 5.4, which should support it fine. I don't know the exact kernel version where support would start, but if you're adding a specific check on 18.04, you might just make it 18.04 AND a 4.x kernel. |
Well, checking for the kernel on the machine will happen at install time, and that'd need me to write some post-install scriptlet I guess, which I haven't done before on the debian side. Is it a deal-breaker to skip |
I think we can uncomment it unconditionally on 18.04. Users can enable if needed. I think we can close. Please reopen if I am mistaken. |
I can still reproduce this error on ubuntu 18.04:
This blocks ceph/ceph#39494 |
Is there a reason you need to support this? We're in the process of deprecating upstream support for 18.04. |
Do you have a supported major version that continues to support 10.08? Ceph Octopus is supposed to be EOL mid 2022. And 18.04 is EOL in 2028 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
On a clean installation of podman 3, all commands fail when executed as root.
Steps to reproduce the issue:
Describe the results you received:
From the podman error message, it seems like there is a test to determine kernel support for "metacopy", but it fails with an untrapped error on systems that don't offer that option?
Reverting
mountopt = "nodev,metacopy=on"
(v3) in/etc/containers/storage.conf
tomountopt = "nodev"
(as it installed in 2.2) avoids the issue.Describe the results you expected:
sudo podman <command>
should function, or at least an explicit "metacopy support not present, manually edit storage.conf" message could print.Additional information you deem important (e.g. issue happens only occasionally):
Root is still required for checkpointing, and checkpointing with overlayfs via criu has been broken in ubuntu kernels since somewhere in the 5.0.0-2x range. 4.15.x is soon to be the only still-maintained (4.4.x has a few months left), working LTS ubuntu kernel for overlayfs checkpoints. From what I can gather, metacopy was added in 4.19
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
google cloud ubuntu-1804 image, ga (4.15.x) kernel
The text was updated successfully, but these errors were encountered: