Skip to content

Commit

Permalink
Document on how to integrate with docker/build-push-action (#90)
Browse files Browse the repository at this point in the history
This change adds some extra clarification to the documentation to show how to setup the `docker/build-push-action` step with this action. This is very helpful when using buildkit's `RUN --mount=type=ssh`. We found this to be a little confusing and the GH issues we found on the matter didn't help!

Co-authored-by: Matthias Pigulla <mp@webfactory.de>
  • Loading branch information
johnhamelink and mpdude committed Nov 18, 2021
1 parent bbd5513 commit 97348a2
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,19 @@ If you know that your favorite tool or platform of choice requires extra tweaks

If you are using this action on container-based workflows, make sure the container has the necessary SSH binaries or package(s) installed.

### Using the `docker/build-push-action` Action

If you are using the `docker/build-push-action`, and would like to pass the SSH key, you can do so by adding the following config to pass the socket file through:

```
- name: Build and push
id: docker_build
uses: docker/build-push-action@v2
with:
ssh: |
default=${{ env.SSH_AUTH_SOCK }}
```

### Cargo's (Rust) Private Dependencies on Windows

If you are using private repositories in your dependencies like this:
Expand Down

0 comments on commit 97348a2

Please sign in to comment.