-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Windows buildkit: copy context error #4918
Comments
What's the contents of your Dockerfile? It's hard to understand what you are trying to achieve as well as you are creating file as Dockerfile but then passing Dockerfile.windows.build.qt-6.5.5-static as filename, although that looks unrelated to the error. Fill in the version/architecture/how you are running buildkit info as requested by the template. If you are building windows containers (not windows client building linux containers) then this is not supported by |
Sorry, the mismatching Dockerfile name has been due to my incomplete preparation for the ticket report. Fixed above. Not sure what you mean with version (in my opinioin already given by 26.1.0 and 0.14.0), architecture (Windows 11). Yes, I'm trying to build a Windows container: otherwise I wonder what that Windows buildx 0.14.0 can be used for ... ? |
Sorry, the mismatching Dockerfile name has been due to my incomplete preparation for the ticket report. Fixed above. Not sure what you mean with version (in my opinion already given by 26.1.0 and 0.14.0), architecture (Windows 11). Yes, I'm trying to build a Windows container: otherwise I wonder what that Windows buildx 0.14.0 can be used for ... ? |
@HeikoNardmann -- which guide are you following, this ( Could you follow this? https://docs.docker.com/build/buildkit/#buildkit-on-windows |
No, I want to create a Windows container on a Windows system using buildkit. |
Ok, please share your repro dockerfile. |
On Windows 11 with docker engine v26.1.0 and buildx v0.14.0 inside
cmd
I run the following:That gives me
Any idea?
The text was updated successfully, but these errors were encountered: