Contributing guidelines <li class="task-list-ite

<div class="highlight highlight-source-yaml notranslate position-relative overflow-auto" dir="auto"

I have change my action to: <div class="highlight highlight-source-yaml notranslat

Self-signed certificates do not work about build-push-action HOT 4 OPEN

53845714nF commented on June 12, 2024

Self-signed certificates do not work

from build-push-action.

Comments (4)

crazy-max commented on June 12, 2024

          config-inline: |
             [registries.insecure]
              "git.fritz.box" = true

BuildKit config does not look correct, see https://docs.docker.com/build/buildkit/configure/#setting-registry-certificates and https://docs.docker.com/build/buildkit/toml-configuration/ for more info.

from build-push-action.

53845714nF commented on June 12, 2024

I have change my action to:

steps:
      - name: Checkout
        uses: https://github.com/actions/checkout@v4
      - name: Set up Docker Buildx
        uses: https://github.com/docker/setup-buildx-action@v3
        with:
          driver-opts: network=host
          config-inline: |
             debug = true
             [registry."git.fritz.box"]
              ca=["/etc/ssl/certs/rootCA.pem"]

And my act_runner config to:

container:
  # Specifies the network to which the container will connect.
  # Could be host, bridge or the name of a custom network.
  # If it's empty, act_runner will create a network automatically.
  network: ""
  # Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
  privileged: false
  # And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).
  options: --mount type=bind,source=/etc/ssl/certs/,target=/etc/ssl/certs/,readonly --mount type=bind,source=/home/rar/gittea.crt,target=/etc/my_certs/gittea.crt,readonly --mount type=bind,source=/home/rar/gittea.key,target=/etc/my_certs/gittea.key,readonly
  valid_volumes:
    - '**'

I think I've made a little progress but i get this 401 error:

failed with: ERROR: failed to solve: failed to push git.fritz.box/frontend:latest: unexpected status from HEAD request to https://git.fritz.box/v2/frontend/blobs/sha256:18fbd407def3017149f5c4ed3ec8777724268e7bcfbd376021df40e27d5be4e1: 401 Unauthorized

from build-push-action.

53845714nF commented on June 12, 2024

I realised that the current error has more to do with the login.

I try to add:

- name: Login to Registry
   uses: https://github.com/docker/login-action@v3
    with:
      registry: git.fritz.box
       username: ${{ secrets.USERNAME }}
       password: ${{ secrets.PASSWORD }}

But I get this:
::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

Can't trace this because he also uses the docker to build.

from build-push-action.

Recommend Projects