Skip to content

docs: state that the buildx settings are ignored in BuildKit mode - #417

Closed
alexey-igrychev wants to merge 1 commit into
mainfrom
docs/server/buildkit-mode-ignores-buildx-settings
Closed

docs: state that the buildx settings are ignored in BuildKit mode#417
alexey-igrychev wants to merge 1 commit into
mainfrom
docs/server/buildkit-mode-ignores-buildx-settings

Conversation

@alexey-igrychev

Copy link
Copy Markdown
Member

The buildkitd section in QUICKSTART (en/ru) says no builder is provisioned per build, but not what that means for the TRDL_BUILDX_DRIVER and TRDL_BUILDX_DRIVER_OPTS_* settings documented right above it: with buildkitd_address set they have no effect at all. One sentence in each locale, so a driver that is configured and then unused does not read as a bug.

Note for #412: once the driver is settable through configure too, this sentence has to name those fields as well.

The buildkitd section says no builder is provisioned per build, but not what
that means for the buildx driver settings documented right above it: with an
address set they are silently without effect, which reads as a bug to anyone
who configured a driver and sees it unused.

Signed-off-by: Aleksei Igrychev <aleksei.igrychev@palark.com>
@alexey-igrychev

Copy link
Copy Markdown
Member Author

Closing this: the sentence mostly repeats what the same section already states two paragraphs above ("no builder is provisioned or removed per build"), and it would need rewriting the moment #412 makes the driver a configure field.

The underlying problem is real, but documentation is the wrong tool for it — filed as a validation requirement instead.

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.

1 participant