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.

Sign up for GitHub

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

Jump to bottom

First podman invocation: Error: overlay test mount with multiple lowers failed, but succeeded with a single lower #10248

Closed
edsantiago opened this issue May 6, 2021 · 4 comments
Closed

First podman invocation: Error: overlay test mount with multiple lowers failed, but succeeded with a single lower #10248

edsantiago opened this issue May 6, 2021 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. rootless

Comments

@edsantiago
Copy link
Member

On Ubuntu-old (with cgroups v1 and runc; possibly with other weird settings), the very very first time rootless podman is invoked, it emits a level=error message (but succeeds with exit 0 regardless):

$  podman version
time="2021-05-06T13:13:04Z" level=error msg="overlay test mount with multiple lowers failed, but succeeded with a single lower"
Version:      3.2.0-dev
...

I can't reproduce on RHEL 8.4, possibly because I can't get a recent-enough version of podman. This looks like a very new error.

The message does not seem to happen after the first invocation of podman.
@edsantiago edsantiago added rootless kind/bug Categorizes issue or PR as related to a bug. labels May 6, 2021
@edsantiago
Copy link
Member Author

Real-world failure. And another one.

edsantiago added a commit to edsantiago/libpod that referenced this issue May 6, 2021
@edsantiago
CI: run rootless tests under ubuntu
95a50a9 
Reason: to catch errors before they surface in RHEL.

One of the Ubuntus is specially crafted to run with cgroups v1
and runc. Although this isn't quite the same as RHEL, it's as
close as we can come in our CI environment, and I suspect it
would have caught containers#10234 (a regression).

Sorry, team.

Also: play kube limits test: skip on all rootless, not just
rootless+fedora. There was a complicated and unnecessary
check in there for Fedora.

Also: workaround for bug containers#10248, a spurious error message on
the first invocation of rootless podman on Ubuntu.Old

Signed-off-by: Ed Santiago <[email protected]>
@Luap99
Copy link
Member

Luap99 commented May 7, 2021

I think this was already fixed by @rhatdan

@rhatdan
Copy link
Member

rhatdan commented May 7, 2021

Fixed in containers storage c36df2f04523a38b2edda2445a899bc63d79448d

@rhatdan rhatdan closed this as completed May 7, 2021
@rhatdan
Copy link
Member

rhatdan commented May 7, 2021

containers/storage#885

@edsantiago edsantiago mentioned this issue May 10, 2021
Merged
edsantiago added a commit to edsantiago/libpod that referenced this issue May 10, 2021
@edsantiago
Remove obsolete skips
471f489 
The following bugs seem to be fixed:

* containers#6510 (e2e tests) - podman rmi gives "layer not known"

* containers#9915 (buildah-bud tests) - podman build --arch

* containers#10248 - spurious warning from first-ever invocation
  of rootless podman

Signed-off-by: Ed Santiago <[email protected]>
@tobwen tobwen mentioned this issue May 24, 2021
Closed
@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 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. rootless
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edsantiago @rhatdan @Luap99