Specifying Act Server Path Broken and/or stale workspace #2620
Open
Description
Bug report info
act version: 0.2.70
GOOS: linux
GOARCH: amd64
NumCPU: 16
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
Config files:
/home/bstrausser/.actrc:
-P ubuntu-latest=catthehacker/ubuntu:act-latest
-P ubuntu-22.04=catthehacker/ubuntu:act-22.04
-P ubuntu-20.04=catthehacker/ubuntu:act-20.04
-P ubuntu-18.04=catthehacker/ubuntu:act-18.04
Build info:
Go version: go1.21.13
Module path: github.com/nektos/act
Main version: (devel)
Main path: github.com/nektos/act
Main checksum:
Build settings:
-buildmode: exe
-compiler: gc
-ldflags: -s -w -X main.version=0.2.70 -X main.commit=9c7f103bb39f11430f58c1a68d5629a42e6d56a1 -X main.date=2024-12-01T02:37:38Z -X main.builtBy=goreleaser
CGO_ENABLED: 0
GOARCH: amd64
GOOS: linux
GOAMD64: v1
vcs: git
vcs.revision: 9c7f103bb39f11430f58c1a68d5629a42e6d56a1
vcs.time: 2024-12-01T02:37:19Z
vcs.modified: false
Docker Engine:
Engine version: 24.0.7
Engine runtime: runc
Cgroup version: 2
Cgroup driver: systemd
Storage driver: overlay2
Registry URI: https://index.docker.io/v1/
OS: Ubuntu 22.04.3 LTS
OS type: linux
OS version: 22.04
OS arch: x86_64
OS kernel: 6.5.0-35-generic
OS CPU: 16
OS memory: 31807 MB
Security options:
name=apparmor
name=seccomp,profile=builtin
name=cgroupns
Command used with act
./bin/act push -e ci/event_changes.json --pull=false --secret-file ci/.secrets --env-file ci/.env --var-file ci/.vars --artifact-server-path /tmp/artifacts
Describe issue
My original issue was that files in the workspace were stale. Meaning I could commit a file to my local branch, but it would not appear in the workspace after artifact copy.
This was working well when originally using --artifact-server-path /tmp/artifacts
I wanted to change directories so I changed the path. That broke. I attempted to switch back
I have tried killing the artifact server container and docker prune. Then tried running with the --rm
flag. I also removed the directories under /tmp/artifacts
I'm sure there are other levels of caching or cleanup I'm missing.
Link to GitHub repository
No response
Workflow content
- name: Upload entire workspace
uses: actions/upload-artifact@v4
with:
name: workspace
path: .
...
- name: Download workspace
uses: actions/download-artifact@v4
with:
name: workspace
Relevant log output
[Embedded Software/release ] 💬 ::debug::[Request] ListArtifacts http://192.168.65.132:34567/twirp/github.actions.results.api.v1.ArtifactService/ListArtifacts
2025/01/15 14:14:54 http: panic serving 192.168.65.132:50422: open /tmp/artifacts/1: no such file or directory
goroutine 7021 [running]:
net/http.(*conn).serve.func1()
/opt/hostedtoolcache/go/1.21.13/x64/src/net/http/server.go:1873 +0xb9
panic({0xd2a880?, 0xc00061d1d0?})
/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/panic.go:920 +0x270
github.com/nektos/act/pkg/artifacts.(*artifactV4Routes).listArtifacts(0xc000363900, 0x0?)
/home/runner/work/act/act/pkg/artifacts/arifacts_v4.go:372 +0x577
github.com/nektos/act/pkg/artifacts.RoutesV4.func3({0xfb2630?, 0xc0002d8000?}, 0xc000432000?, {0x4?, 0x6e1483247?, 0xc1da202b8e8b35ce?})
/home/runner/work/act/act/pkg/artifacts/arifacts_v4.go:168 +0x47
github.com/julienschmidt/httprouter.(*Router).ServeHTTP(0xc000126a80, {0xfb2630, 0xc0002d8000}, 0xc00035c500)
/home/runner/go/pkg/mod/github.com/julienschmidt/httprouter@v1.3.0/router.go:387 +0x7eb
net/http.serverHandler.ServeHTTP({0xfb03d0?}, {0xfb2630?, 0xc0002d8000?}, 0x6?)
/opt/hostedtoolcache/go/1.21.13/x64/src/net/http/server.go:2943 +0x8e
net/http.(*conn).serve(0xc00013c5a0, {0xfb4a58, 0xc0001c46c0})
/opt/hostedtoolcache/go/1.21.13/x64/src/net/http/server.go:2014 +0x5f4
created by net/http.(*Server).Serve in goroutine 10
/opt/hostedtoolcache/go/1.21.13/x64/src/net/http/server.go:3091 +0x5cb
[Embedded Software/release ] ❗ ::error::Unable to download artifact(s): Failed to ListArtifacts: Unable to make request: ECONNRESET%0AIf you are using self-hosted runners, please make sure your runner has access to all GitHub endpoints: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github
### Additional information
_No response_