-
Notifications
You must be signed in to change notification settings - Fork 7.6k
docs: added note on populating builds tab when building windows container images #22389
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
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Thank you @chaomonica!
@chaomonica Would you like me to merge this now, or do you want me to wait for @karman-docker approval too? |
looks good to me. @chaomonica I am assuming you have tested this with |
@karman-docker Yes, it has been tested, thanks! |
Description
If a user switches to Windows containers and builds an image using the
docker build
command as it (using the legacy builder), the Builds tab is not populated. This is because the build history is provided by Buildkit. To populate the Builds tab, the customer must either setDOCKER_BUILDKIT=1
or use thebuildx build
command.Current documentation does not mention this and a support ticket was raised.
Related issues or tickets
Reviews