|
It just fails with... Is it anything on my side or is it just a broken docker image? PS: Also issue template says bugs for v3 are not currently accepted (wails-cross is v3 feature, right?); and Discord URL listed in templates is highly suspicious because attempting to join it logs me out of Discord account on all devices and forces account re-verification. That doesn't really invite to touch Wails at all... |
Replies: 1 comment
|
This looks like Docker's legacy builder encountering a First check that Buildx is available: docker buildx versionThen, from the project directory, retry with BuildKit explicitly enabled (POSIX shell): DOCKER_BUILDKIT=1 wails3 task setup:dockerIf that reports a missing or broken Buildx component, install or repair the Buildx plugin. Docker documents how a missing Buildx component can cause older Docker installations to fall back to the legacy builder. If an older BuildKit frontend still rejects the heredoc, put This should address the specific |
This looks like Docker's legacy builder encountering a
COPYheredoc. TheStep 11/23output is a clue:<<'ZIGWRAP'starts an inline file in the Dockerfile, and needs a builder/frontend that supports that syntax.First check that Buildx is available:
Then, from the project directory, retry with BuildKit explicitly enabled (POSIX shell):
If that reports a missing or broken Buildx component, install or repair the Buildx plugin. Docker documents how a missing Buildx component can cause older Docker installations to fall back to the legacy builder.
If an older BuildKit frontend still rejects the heredoc, put
# syntax=docker/docker…