daemon/graphdriver: don't unmount graphdriver root #41903
Draft
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.
depends on moby/sys#62
fixes #39267
Most graphdrivers no longer re-mount the graphdriver root, so we should not try to unmount the root itself, to allow users to mount a custom storage location at the graphdriver's root.
Some exceptions:
all mounts https://github.com/moby/moby/blob/v20.10.2/daemon/graphdriver/devmapper/deviceset.go#L2245-L2277
NOTE: Perhaps no unmounting is needed at all, looking at;
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)