"Ignoring global metacopy option, not supported with booted kernel"

[edsantiago]

Seen twice this month, ubuntu root only:

# podman something
time="2022-08-23T09:23:53Z" level=warning msg="Ignoring global metacopy option, not supported with booted kernel"

When this happens, a ton of tests fail.

• ubuntu-2204 : sys podman ubuntu-2204 root host
  • PR Improved Windows compatibility #15372
    • 08-23 05:27
  • PR build(deps): bump github.com/mattn/go-isatty from 0.0.14 to 0.0.16 #15319
    • 08-15 09:34

Seems likely to be a system problem, i.e., the Ubuntu VM booted up in some broken manner. Filing as a placeholder but I have no time to poke into Cirrus VMs right now.

[edsantiago]

Another one, f36 aarch64 root

[edsantiago]

Another one, f36 root

[edsantiago]

f36 root again

[edsantiago]

Big flake trio just now, f36 x86, f36 aarch64, and ubuntu 2204, all root, all failed on rerun. EDIT never mind, this is a real bug, #15698

[edsantiago]

Real flake here: f36 aarch64 root. Begins in test 324, "sensitive mount points are masked without --privileged". All tests ran fine up to that point, all tests failed after that point.

[edsantiago]

Another one, f36 aarch64 root, begins in test 322 which is the same as above ("sensitive etc").
And another, same everything, except f36 normal, not aarch64

[edsantiago]

The common factor is that things first go bad in this test:

podman/test/system/400-unprivileged-access.bats

Line 104 in 6d8bafe

@test "sensitive mount points are masked without --privileged" {

The problem could be triggering there, or in an earlier test. (Definitely not the podman container storage is not accessible by unprivileged users test, because that one is skipped on Ubuntu, and we see this flake on Ubuntu). I've been running the 320, 330, and 400 tests in a loop on my f36 laptop, and have not been able to reproduce the flake.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[Ji993]

I also experienced a similar issue.
To replicate:

1. Uncomment mount_program = "/usr/bin/fuse-overlayfs" in /etc/containers/storage.conf
2. podman container run -d -it <<some_image>>
3. Now every time you do a run or some other container-related operation you will keep getting the warning message "WARN[0000] Ignoring global metacopy option, not supported with booted kernel"

Resolution:

1. Comment the # mount_program = "/usr/bin/fuse-overlayfs" in /etc/containers/storage.conf
2. Stop all containers and pods.
3. rm -rf /run/containers /var/lib/containers /home/<>/{.config,.cache,.local}
4. Uninstall/Reinstall podman

OS: RHEL 9.1
Kernel: 5.14.0-162.6.1.el9_1.x86_64
Podman: v4.2.0

[rhatdan]

@giuseppe PTAL

[giuseppe]

it is fixed upstream with containers/storage@c267eed

that was vendored by eb28a1c