docs: added note on populating builds tab when building windows container images #22389
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
area/desktop
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
aevesdocker
reviewed
Apr 9, 2025
aevesdocker
approved these changes
Apr 9, 2025
|
@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
approved these changes
Apr 9, 2025
|
@karman-docker Yes, it has been tested, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If a user switches to Windows containers and builds an image using the
docker buildcommand 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=1or use thebuildx buildcommand.Current documentation does not mention this and a support ticket was raised.
Related issues or tickets
Reviews