On 2025-05-25 14:45, Santiago Vila wrote:
El 25/5/25 a las 19:32, Reinhard Tartler escribió:
Any idea why this might work for me when using the unshare backend?
No idea, but I asked the failing function to print the options
themselves, like this:
- if len(m.Options) != 1 {
- t.Errorf("expected 1 mount option but got %d",
len(m.Options))
- }
+ if len(m.Options) != 1 {
+ t.Fatalf("expected 1 mount option but got %d: %+v",
len(m.Options), m.Options)
+ }
and it showed this:
=== RUN TestOverlayView
snapshot_test.go:696: expected 1 mount option but got 2:
[lowerdir=/tmp/TestOverlayView2389272231/001/snapshots/2/fs:/tmp/TestOverlayView2389272231/001/snapshots/1/fs
userxattr]
Is this meaningful for you?
Not sure. It tells me that there are some systems configurations where
the system (probably kernel) is injecting "default" mount attributes by
default. I don't have the bandwidth to research this in details at this
point, and decided to comment out this particular check.
It also appears that the most recent revision of the test does not have
significant changes upstream. As such, I suspect the issue is likely to
be present there as well.
Please do let me know if there is something I may have missed or whether
there is a way to improve the test, ideally in a way that can be
upstreamed.
