Juan Abadie

I think you just need to provide the full path to the image. Please look at the registry and give the full name (tag included)

Hey @aradhakrishnanGFDL . Thanks for reporting the issue. I haven't used the action in AWS for a while now, but looking at [the example I wrote in the readme](https://github.com/whoan/docker-build-with-cache-action#aws-ecr) you...

@estrehle I don't remember to have dealt with permission issues when I tested the actin in aws. Did you came up with the minimal cfg needed to run the action...

You have a very valid point @mdegis . I will take a look sometime soon. I think we need `docker buildx` to do so. Feel free to make suggestions/PR.

@mdegis I think this action does what you want: https://github.com/docker/setup-buildx-action

@bob-bins I should allow something like JSON in `build_extra_args` to support your use case. I can give it a try today or tomorrow. On the other hand, using an env...

With `ARG` you will have the secret as part of your image, with [`ENV`](https://docs.docker.com/engine/reference/builder/#env) you can override/set with `docker run --env =`

Not really as you don't have to run `docker run` in the action. In addition, you have options to _forward_ the environment variable to the container: - `docker run -e...

@bob-bins Could you please try with branch [support-json-for-extra-build-args](https://github.com/whoan/docker-build-with-cache-action/tree/support-json-for-extra-build-args)? - uses: whoan/docker-build-with-cache-action@support-json-for-extra-build-args You will have to use something like this: build_extra_args: '{"--build-arg": "myarg=Hello\nWorld"}'

@anton-buyskikh `DUMMY_IMAGE_NAME` is used internally up to the point where it is renamed/tagged to the correct name: https://github.com/whoan/docker-build-with-cache-action/blob/7210dca924e2463bb97970841b186e824b9411a8/docker-build.sh#L102 What's the issue concern here? Is it just the log being misleading?