-
Notifications
You must be signed in to change notification settings - Fork 64
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
RUN --mount support in Windows BuildKit #498
Comments
Cross-linking moby/buildkit#4837 |
This issue has been open for 30 days with no updates. |
Still on the backlog, will update when we have something working. |
This issue has been open for 30 days with no updates. |
Still on the backlog. |
This issue has been open for 30 days with no updates. |
2 similar comments
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
Closing this as it's being tracked in the buildkit repo: moby/buildkit#4837 |
The following comment written in the issue for adding Windows BuildKit support indicated that in the future, we might be able to expect support for caching
RUN
steps via the--mount
option. However, I am still unable to use the--mount
option forRUN
commands in Windows. Is support for this planned?That is correct, currently Windows only supports mounting physical/virtual devices and named pipes/host folders via VSMB. The default mount type on Linux when none is explicitly specified is
bind
. On Windows it'swindows-layer
. While bind mounts on Linux are common place and can be used in any number, on Windows,windows-layer
have only ever been used as root filesystem mounts.It may suffice to allow setting the mount type in
llb
state. But I have not looked too much into it. Will have a look soon. I suspect we'll hit this issue when enabling tests as well.That is already being worked on by @profnandaa (see moby/buildkit#4432) and there should be a number of PRs incoming that will at least hook up the test suite to the CI and lay the ground for enabling tests (some will already be enabled, some should run but require support - images, windows specific testing Dockerfiles, etc).
Originally posted by @gabriel-samfira in #34 (comment)
The text was updated successfully, but these errors were encountered: