Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

act unable to run on rancher desktop / containerd #2077

Open
villanisaac-kr opened this issue Nov 3, 2023 · 3 comments
Open

act unable to run on rancher desktop / containerd #2077

villanisaac-kr opened this issue Nov 3, 2023 · 3 comments
Labels
kind/bug Something isn't working

Comments

@villanisaac-kr
Copy link

villanisaac-kr commented Nov 3, 2023

Bug report info

act version:            0.2.53
GOOS:                   darwin
GOARCH:                 arm64
NumCPU:                 10
Docker host:            unix:///Users/[REDACTED]/.rd/docker.sock
Sockets found:
        /var/run/docker.sock
Config files:           
Build info:
        Go version:            go1.21.3
        Module path:           command-line-arguments
        Main version:          
        Main path:             
        Main checksum:         
        Build settings:
                -buildmode:           exe
                -compiler:            gc
                -ldflags:             -X main.version=0.2.53
                DefaultGODEBUG:       panicnil=1
                CGO_ENABLED:          1
                CGO_CFLAGS:           
                CGO_CPPFLAGS:         
                CGO_CXXFLAGS:         
                CGO_LDFLAGS:          
                GOARCH:               arm64
                GOOS:                 darwin

Error: error during connect: Get "http://%2FUsers%2F[REDACTED]%2F.rd%2Fdocker.sock/v1.24/info": EOF

Command used with act

act  -j test -W \
  .github/workflows/test-bootstrap-actions-suite.yaml \
  -s GITHUB_TOKEN="$GH_TOKEN" \
  --secret-file local.secrets  \
  --input-file local.inputs  \
  -P kubernetes=[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64  \
  -P aks=[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64  \
  --pull=false \
  --container-architecture linux/arm64

Describe issue

Getting below error when executing act. Using Rancher Desktop as my docker engine.

Error: unable to determine if image already exists for image '[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64' (linux/arm64): error during connect: Get "http://%2FUsers%2F[REDACTED]%2F.rd%2Fdocker.sock/v1.24/images/[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64/json": EOF

Link to GitHub repository

No response

Workflow content

n/a. The workflows run on act when using Docker desktop. But Our company is restricting the use of docker desktop and using rancher desktop instead. 

#docker-compose.yaml
---
version: "3"
services:
  runner:
    image: [REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64
    privileged: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - act-net

Relevant log output

Test bootstrap actions suite/test] 🚀  Start image=[REDACTED]]/workflow-test-runner:debian-bullseye-1.3.0_arm64
INFO[0000] Parallel tasks (0) below minimum, setting to 1 
[Test bootstrap actions suite/test]   🐳  docker pull image=[REDACTED]/workflow-test-runner:debian
Error: unable to determine if image already exists for image '[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64' (linux/arm64): error during connect: Get "http://%2FUsers%2F[REDACTED]%2F.rd%2Fdocker.sock/v1.24/images/[REDACTED]/workflow-test-runner:debian-bullseye-1.3.0_arm64/json": EOF

Additional information

No response

@villanisaac-kr villanisaac-kr added the kind/bug Something isn't working label Nov 3, 2023
@villanisaac-kr villanisaac-kr changed the title act act unable to run on rancher desktop / containers Nov 3, 2023
@villanisaac-kr villanisaac-kr changed the title act unable to run on rancher desktop / containers act unable to run on rancher desktop / containerd Nov 3, 2023
@emont01
Copy link

emont01 commented Jan 8, 2024

Try defining the variable DOCKER_HOST either before running act:

export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}')
act -j test ...

or as a one liner:

DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') act -j test ...

@jsoref
Copy link
Contributor

jsoref commented Jan 28, 2024

It'd be really nice if act honored the active docker context instead of relying on manually setting DOCKER_HOST or creating a symlink in /var/run/docker.sock ...

@jsoref
Copy link
Contributor

jsoref commented Jan 28, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants