-
Notifications
You must be signed in to change notification settings - Fork 58
feat: support arbitrary mount options for each cache #28
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
feat: support arbitrary mount options for each cache #28
Conversation
4716303 to
57d2f8c
Compare
Signed-off-by: Amin Yahyaabadi <[email protected]>
Signed-off-by: Amin Yahyaabadi <[email protected]>
Signed-off-by: Amin Yahyaabadi <[email protected]>
2ff6d18 to
cfc6f5e
Compare
Signed-off-by: Amin Yahyaabadi <[email protected]>
Signed-off-by: Amin Yahyaabadi <[email protected]>
d086e9f to
d2e9ac7
Compare
Signed-off-by: Amin Yahyaabadi <[email protected]>
4020c7e to
2a1e987
Compare
|
@AkihiroSuda Any more comment on this? |
AkihiroSuda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
|
Thanks @aminya for exposing all the mount arguments. As it turns out, I needed to set both the cash ID and sharing mode to match my Dockerfile in order for the cash injection and extraction to utilize the correct cash mount. Perhaps the sharing mode is included in the derivation of the internal cash key. Needless to PR now gives us that flexibility! |
|
You're welcome! It's cool to see another robotics engineer using these tools. I find the path parameter usually enough for my use cases, but feel free to document your findings in the readme. |
Fixes #12
Closes #21