buildx
buildx copied to clipboard
docker
Docker CLI plugin for extended build capabilities with BuildKit
 Why did the build go wrong, buildx didn't exit properly, and subsequent commands could continue? buildx version:github.com/docker/buildx v0.8.2 buildkit verison: v0.9.1 buildx --driver kubernetes mode
Hey, I'm trying to use `buildx` to do some multi-arch builds in our infrastructure. We use Google Container Registry which configures credHelpers like so: ``` bash-4.2$ cat ~/.docker/config.json { "auths":...
Currently `bake --push` will tag images in the remote registry as they are completed. This can be an issue if later images in the same high-level build error out. Either...
This is something I end up doing a lot: ```hcl target "foo" { tags = defaultTagsFor("foo") } ``` it'd be useful to have some scoped variable here representing the target's...
To use a [Composer ](https://getcomposer.org) auth token in my build I need to mount a file something like this into the right location in the container: ```json {"github-oauth":{"github.com":"${GITHUB_TOKEN }"} }...
The error message emitted by buildx if the syntax is invalid is not as good as it could be. It does not state that it is the secret itself that...
This issue is more comprehensively described in the below linked issue, but since it appears to be an issue in buildx itself, I've opened an issue here to track. Hope...
The [compose spec section about project names](https://github.com/compose-spec/compose-spec/blob/5260c1bc8ee5e93ce88412bb460924e9535d9080/spec.md#name-top-level-element) says: > [the project name] MUST be exposed for [interpolation](https://github.com/docker/buildx/issues/new#interpolation) and environment variable resolution as COMPOSE_PROJECT_NAME This would be pretty handy for one...
When trying to build and push an image defined by these compose files: ```yaml # docker-compose.yaml services: myservice: build: . image: myimage:dev ``` ```yaml # docker-compose.myregistry.yaml services: myservice: image: myregistry/myimage:latest...
buildx can't push to artifactory or other repos that don't have /oauth/token as their token endpoint
When pushing final image using `docker buildx build` to an enterprise artifactory docker registry, auth seems to fail I suspect that the request is looking directly for `/oauth/token` endpoint, regardless...
