Hi, it would be nice to add support for registries served only over http instead of ht

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

If you're using a <a href="https://github.com/docker/build-push-action/#local-registry

Feature request: Insecure registry about login-action HOT 2 CLOSED

docker commented on June 4, 2024

Feature request: Insecure registry

from login-action.

Comments (2)

crazy-max commented on June 4, 2024 2

@danbalarin If you try to login to an insecure registry, it’s not possible with basic authentication..

If you want to pull or push an image you can set your registry as insecure in a step before:

name: ci

on:
  push:
    branches: master

jobs:
  login:
    runs-on: ubuntu-latest
    steps:
      -
        name: Set insecure registry
        run: |
          echo "{ \"insecure-registries\": [\"${{ secrets.DOCKER_REGISTRY }}\"] }" | sudo tee /etc/docker/daemon.json
          sudo service docker restart
      -
        name: Pull
        run: |
          docker pull ${{ secrets.DOCKER_REGISTRY }}/myimage:latest

But this is very insecure and is not recommended.

from login-action.

crazy-max commented on June 4, 2024 1

If you're using a local registry in your workflow for testing purposes you can use the build push action and do that instead:

name: ci

on:
  push:
    branches: master

jobs:
  local-registry:
    runs-on: ubuntu-latest
    services:
      registry:
        image: registry:2
        ports:
          - 5000:5000
    steps:
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
        with:
          driver-opts: network=host
      -
        name: Build and push to local registry
        uses: docker/build-push-action@v2
        with:
          push: true
          tags: localhost:5000/name/app:latest
      -
        name: Inspect
        run: |
          docker buildx imagetools inspect localhost:5000/name/app:latest