ilteoood / docker_buildx Goto Github PK

So when trying to use this action to buld a docker image the build fails with the follwing error message:

#31 pushing layers
#31 pushing layers 0.3s done
#31 ERROR: server message: insufficient_scope: authorization failed
------
 > exporting to image:
------
failed to solve: rpc error: code = Unknown desc = server message: insufficient_scope: authorization failed
##[error]Command failed: docker_buildx/scripts/docker_build.sh linux/amd64,linux/arm64,linux/arm/v7 recipes test Dockerfile true none

The full log can be found here, the action file in question is this one.

I have searched for the error message and have found various issues 1 2 but have not been able to fix this.

Any ideas on what could be causing this issue ? Thanks very much in advance!

It would be nice if this supported the build(x) option --target. I currently use a multi-stage Dockerfile to build each tag from a single file (the first stage installs all the deps/etc, so it makes sense to use one Dockerfile). Then I build like so:

docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t iggy/image1:latest --target stage1 --pull --push .
docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t iggy/image2:latest --target stage2 --pull --push .

This is a great little utility, but I'm having trouble getting it to work. You can see the repo and build results, or read on. Here's the config I used:

      - uses: ilteoood/[email protected]
        with:
          tag: ${{ matrix.tags }}
          imageName: cjyar/openldap
          buildArg: ALPINE_VERSION=${{ matrix.alpine }},OPENLDAP_VERSION=${{ matrix.openldap }}
          publish: ${{ (github.event_name == 'push' && github.ref == 'refs/heads/master') || github.event_name == 'workflow_dispatch' }}
          dockerHubUser: cjyar
          dockerHubPassword: ${{ secrets.DOCKER_PASSWORD }}

It said: Error: Command failed: docker_buildx/scripts/dockerhub_login.sh cjyar ***

my yml file Build Image.yml
when i use it ,it is not work.this logs:

actions_builder
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 1.5s done
#1 creating container buildx_buildkit_actions_builder0
#1 creating container buildx_buildkit_actions_builder0 1.7s done
#1 DONE 3.2s
Supported platforms:  linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
WARNING! Your password will be stored unencrypted in /home/runner/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
"docker buildx build" requires exactly 1 argument.
See 'docker buildx build --help'.

Usage:  docker buildx build [OPTIONS] PATH | URL | -

Start a build
##[error]Command failed: docker_buildx/scripts/docker_build.sh linux/arm64,linux/amd64 ***/qiandao latest Dockerfile true none false 

how can i solve it?

I thought you should know... I am getting a warning on execution but is working:

Check warning on line 1 in .github

@github-actions
github-actions
/ docker-buildx-x86-and-test

.github#L1
Unexpected input 'load', valid inputs are ['tag', 'imageName', 'dockerFile', 'buildArg', 'publish', 'platform', 'dockerHubUser', 'dockerHubPassword']

Would it be possible to add buildx build "--load switch" support to the GitHub Action?

Principal use-case would be to build a "x86" version first and run it through CI tests and then if successful to build it for other platforms using the previous cache.

Would this be possible and easy to do?

The current bash shell implementation withholds the logs until the build step finishes. This is not ideal especially when buildx could be running multi-arch builds in parallel.

Looking at another docker-builx github action (https://github.com/crazy-max/ghaction-docker-buildx), and it doesn't have this issue. Perhaps this will be an easy fix?

At the moment it runs in the root directory and if the dockerfile references files with relative path the build fails.

This can be solved like

docker buildx build --platform $1 $PUSH $LOAD $TAGS $BUILD_ARGS $TARGET -f $4 .

change into

docker buildx build --platform $1 $PUSH $LOAD $TAGS $BUILD_ARGS $TARGET $4

and probably rename arg $4 from docker file into buildContext

This is a stupid question!

The recent rclone release 1.54.1 didn't run the publish action for some reason as yet unknown, so rclone's docker image didn't get built.

I'd like to run it manually, but I can't figure out how - is there some way I can use the code from this action to do it?

I know how to make a normal docker build and upload it but I can't figure out how to use the extra magic here to create more architectures manually.

Thanks