Add note about DM_DISABLE_UDEV to README. #129
Merged
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.
Signed-off-by: Erik Sipsma [email protected]
When working on running our tests in a container, I encountered a bunch of strange race-conditions related to device node creation during the snapshotter tests. This turned out to be due to the udev daemon not being accessible inside the container even though I was bind-mounting /dev from the host to the container.
Another possible fix to this issue would be to change our snapshotter code to use the
--verifyudev
flag for all dmsetup operations. However, it turns out there is an environment variableDM_DISABLE_UDEV
(documented on the lvm(8) man-page only, not dmsetup(8) man-page for some reason), that appears to be a catch-all for making dmsetup and other tools under the lvm umbrella behave well in an environment where udev is not accessible.Given the flexibility of environment variables relative to hardcoding flags in our code, just documenting this behavior feels like the best fix, so this PR is just a README update.
I tested this by running the tests in a docker container (
docker run --rm -it --privileged -v /local/container-tmp:/tmp firecracker-containerd
) where I started the snapshotter inside withDM_DISABLE_UDEV=1
and saw the tests pass consistently:By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.