mountinfo/TestGetMounts: fix for Ubuntu build system #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Apparently, Ubuntu build system is some sort of a chroot which does not have / mount in its /proc/self/mountinfo. This leads to test failure described in moby#17. The fix is not to require a specific mount (even '/' that must exist but apparently does not in some setups). Instead, let's require at least 2 mounts, doesn't matter which ones. For reference, his test case was added by moby/moby#4812 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
|
@thaJeztah @cpuguy83 PTAL |
|
The Linux kernel's show_mountinfo() has a check that the mount is accessible, and it is not shown if not. Looks like this is why the mount for / is not shown in the Ubuntu case -- they have some weird setup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apparently, Ubuntu build system is some sort of a chroot which does not
have
/mount in its /proc/self/mountinfo. This leads to test failuredescribed in #17.
The fix is not to require a specific mount (even
/that must exist butapparently does not in some setups). Instead, let's require at least 2
mounts, doesn't matter which ones.
For reference, his test case was added by
moby/moby#4812
Fixes: #17