Uh oh!
There was an error while loading. Please reload this page.
[master] plugins: don't require "experimental" for buildx - #490
Conversation
Some features of buildx may still be "experimental" / non-final, but we can call those out individually if needed. This change removes the requirement to enable "experimental" mode in the cli configuration file, so that it's easier for users to try buildx. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
thaJeztah
commented
Aug 4, 2020
chris-crone
left a comment
There was a problem hiding this comment.
LGTM
We should update the buildx README too
hakman
commented
Aug 4, 2020
Somewhat related, any thoughts about |
thaJeztah
commented
Aug 4, 2020
Still being discussed; we may remove the "experimental" requirement itself, but there's still (UX) issues with those subcommands that should be looked into, so they may still be marked "experimental" (in the documentation), to indicate that backward-compatibility of the commands is not guaranteed. |
thaJeztah
commented
Aug 4, 2020
@chris-crone yes, I had that one open in a tab; should be updated that starting with 20.x it's not needed to set the configuration (unless we decide to backport this change to 19.03, in which case the patch release version should be mentioned) |
since docker 20.10 buildx is no longer experimental see docker/docker-ce-packaging#490
Some features of buildx may still be "experimental" / non-final, but we can call those out individually if needed.
This change removes the requirement to enable "experimental" mode in the cli configuration file, so that it's easier for users to try buildx.