[GH-ISSUE #2077] act unable to run on rancher desktop / containerd #992

Closed
opened 2026-03-01 21:48:00 +03:00 by kerem · 4 comments
Owner

Originally created by @villanisaac-kr on GitHub (Nov 3, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2077

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

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

Originally created by @villanisaac-kr on GitHub (Nov 3, 2023). Original GitHub issue: https://github.com/nektos/act/issues/2077 ### Bug report info ```plain text 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 ```sh 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 ```yml 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 ```sh 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_
kerem 2026-03-01 21:48:00 +03:00
Author
Owner

@emont01 commented on GitHub (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 ...
<!-- gh-comment-id:1881697703 --> @emont01 commented on GitHub (Jan 8, 2024): Try defining the variable DOCKER_HOST either before running act: ```bash export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') act -j test ... ``` or as a one liner: ```bash DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}') act -j test ... ```
Author
Owner

@jsoref commented on GitHub (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 ...

<!-- gh-comment-id:1913435653 --> @jsoref commented on GitHub (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` ...
Author
Owner

@jsoref commented on GitHub (Jan 28, 2024):

This is:

<!-- gh-comment-id:1913577521 --> @jsoref commented on GitHub (Jan 28, 2024): This is: - [ ] #583
Author
Owner

@github-actions[bot] commented on GitHub (Jul 27, 2024):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:2253666354 --> @github-actions[bot] commented on GitHub (Jul 27, 2024): Issue is stale and will be closed in 14 days unless there is new activity
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#992
No description provided.