Skip to content
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

Mention defaulting to BuildKit #12505

Merged
merged 5 commits into from
Mar 15, 2021

Conversation

stephen-turner
Copy link
Contributor

Proposed changes

Mention that Docker Desktop 3.2.0 defaults to BuildKit.

Related issues

Fixes docker/for-mac#5458

@stephen-turner
Copy link
Contributor Author

stephen-turner commented Mar 15, 2021

@usha-mandya Formatting might need to be improved; I'm not sure of the best way to do a code block within a bullet list. Thanks.

Later: Actually the code block seems to have come out OK on the Netlify. Properly indented.

@netlify
Copy link

netlify bot commented Mar 15, 2021

Deploy preview for docsdocker ready!

Built with commit 50f61f3

https://deploy-preview-12505--docsdocker.netlify.app

@@ -52,6 +52,12 @@ This page contains information about the new features, improvements, known issue
- The Docker Dashboard displays a tip once a week.
- Docker Desktop uses iTerm2 to launch the terminal on the container if it is installed. Otherwise, it launches the default Terminal.App. [docker/roadmap#98](https://github.com/docker/roadmap/issues/98)
- Add experimental support to use the new Apple Virtualization framework (requires macOS Big Sur 11.1 or later)
- BuildKit is now the default builder for all users, not just new installations. It can still be turned off under **Preferences** > **Docker Engine** with a block like
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already started using BuildKit as default in version 3.0.0.
Should we move that more down to the 3.0.0 chapter?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was the default for new installations in 2.4 (and it's documented there). I believe it only became the default for existing users in 3.2.

stephen-turner and others added 3 commits March 15, 2021 18:08
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
@stephen-turner
Copy link
Contributor Author

Thanks, @usha-mandya, I made your suggested changes.

Copy link
Member

@usha-mandya usha-mandya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @stephen-turner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BuildKit set as default builder since 3.2.x
3 participants