Skip to content

CI capabilities test: inconsistent CapBnd #9286

@edsantiago

Description

@edsantiago

First things first: this makes no sense to me. I don't see how this could be a flake; it should either consistently fail or consistently pass on the same machine. Instead, we get one-offs, and the ginkgo retry (so far) always passes.

Symptom:

$ podman-remote run --rm --user bin alpine grep CapBnd /proc/self/status
CapBnd:	00000000800405fb
...
Expected
               <string>: CapBnd: 00000000800405fb
           to contain substring
               <string>: 00000000a80425fb

Source:

podman/test/e2e/run_test.go

Lines 334 to 338 in 68ca906

os.Setenv("CONTAINERS_CONF", "/dev/null")
session := podmanTest.Podman([]string{"run", "--rm", "--user", "bin", ALPINE, "grep", "CapBnd", "/proc/self/status"})
session.WaitWithDefaultTimeout()
Expect(session.ExitCode()).To(Equal(0))
Expect(session.OutputToString()).To(ContainSubstring("00000000a80425fb"))

Environment: so far, only f32 and f33. Always remote.

Decoding: the cap difference is -- surprise! -- CAP_NET_RAW, CAP_MKNOD,CAP_AUDIT_WRITE

cirrus-flake-xref results:

Podman run [It] podman run user capabilities test

Could podman be reading containers.conf even though $CONTAINERS_CONF is explicitly overridden?

Metadata

Metadata

Labels

flakesFlakes from Continuous Integrationkind/bugCategorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remote

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions