-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trident with dockerd configured with --data-root #548
Comments
OK, i have one more relevant Information. If i start docker as the same way but the top folder /test is on the same filesystem. This is different of the filesystem /icvar:
data-root with /test/var_lib_docker is working! |
Hi @olivpass, I checked with the team and the data-root option is not something that Docker passes to the Trident Docker Plugin. This may be a docker bug. |
Hi @gnarl, i think not, because the older trident 20.01 I actual normally use, is working with the described setup. And yes, this is also a relevant information. Excuse me! |
Hi @gnarl, next check, upgrade docker to version 20.10.5-ce. Same:
|
Next Debugging:
There is Mounting volume. definitely wrong: /host/var_lib_docker/plugins/.... In my case it perhaps should be /host/icvar/var_lib_docker/plugins/.... With this Information, i am shure, you know if this is a docker or a trident mistake ;-) Thank you |
More Infos:
I read the code and found following lines:
On my host, i get following:
The documentation for /proc/$$/mountinfo: https://www.kernel.org/doc/Documentation/filesystems/proc.txt
maybe you should use (5) and not (4)? |
Thanks for the feedback. We'll look into this again. |
Hello, I still don't know whether this problem is related to trident or the docker daemon itself, but we have a very similiar issue which was actually not related to the The path to the mountpoint of the filesystem where docker "lives" seems to be stripped from the mountpoint for the trident volume. Examples: To prove the point i created a new filesystem and mounted it to I hope this helps in some way. We worked around this problem by bind-mounting |
This issue is fixed with commit 7842b3f and will be included in the Trident v22.10 release. |
Describe the bug
trident Version 21.01.1 does not work, if dockerd is configured with option --data-root
Environment
Provide accurate information about the environment to help us reproduce the issue.
To Reproduce
dockerd is running with following command line Option --data-root:
you see a missing prefix /icvar on the propagated-mount!
without dockerd option --data-root my setup is working!
The text was updated successfully, but these errors were encountered: