build-push-action | GitHub Action to build and push Docker images with Buildx | Continuous Deployment library

You can reference the imageId as described in the output section of the doc. Just add an id at your current job just for reference, as example:

With docker/build-push-action@v2 you can specify the context and the location of the docker file like so:

As you can see on the Ubuntu-20.04 virtual environment, it is provided with some Rust Tools installed:

Check if this is related to actions/runner issue 1039

Seems like GITHUB_TOKEN works only on default branch... You need to use custom PAT when running on PR branches

Check also if this is similar to this discussion:

It turns out another org member had pushed the same package, which was private by default and was owned by that org member.
Since nobody else could even see the package as existing, we were very confused.

I think this default behavior of new packages being privately owned by the user uploading and not being visible to even the org owners is quite confusing.

If not, try, as described here, to do the push manually, in order to validate your token (with a docker login -u USERNAME -p TOKEN ghcr.io, then a docker push). The GitHub action might then work.

The issue is in the docker/build-push-action@v2 action, which by default ignores the checkout created using the actions/checkout@v2 action:

By default, this action uses the Git context so you don't need to use the actions/checkout action to check out the repository because this will be done directly by BuildKit.

The git reference will be based on the event that triggered your workflow and will result in the following context: https://github.com//.git#.

When you pass a git build context to docker build, it won't include the .git directory.

If you read through the documentation for the docker/build-push-action@v2 action, you'll see that you can override this behavior:

However, you can use the Path context using the context input alongside the actions/checkout action to remove this restriction.

You would need to modify your workflow so that it includes an explicit context: ., like this:

You may be missing steps. I have some repos with a similar setup (i.e. Dockerfile in the top-level directory) but I also run steps to

• checkout
• build (where I now use buildx)
• log into the Docker Hub
• build and push
• and also report and commit a timestamp (to force cache changes)

I include one of these below (source is here. It may not be the most minimal setup but it had been working for me quite reliably, including via scheduled (i.e cron) actions. I am skipping the last two items here (see here for the complete file):

Check here https://github.com/docker/build-push-action#customizing, add comma between the tags..

I have a similar pipeline but when I use docker/build-push-action:

• I have no working-directory param
• I have a context param set to current directory in with map

Could you try to modify your Build and push step like this ?

Well now I feel stupid :)

I got all into thinking about how to solve it by including it on the build-stage of the image, and didn't think of that when you start the built image you can choose to use "volumes" that resides on the machine you are starting the docker image from.

It was as simple as:

1. Copy the folder with my certificate files from my local version of my GitHub repo to the remote version of my repo at my server with SCP, for example:

scp -r $(pwd)/Certificates_prod user@server:/path/to/repo/on/server

1. Go into your docker-compose file and go under the container that is supposed to use the certificate-files and add the folder as a mounted volume, for example: