Open
Description
I have a job that build a golang binaries. After downloading all the dependencies the job failed to cp all dependencies to the cache directory
Minimal .gitlab-ci.yml illustrating the issue
---
.go-cache:
variables:
GOPATH: $CI_PROJECT_DIR/.go
before_script: |
mkdir -p "${GOPATH}"
chown -R :users $CI_PROJECT_DIR
chmod -R a+rwX $CI_PROJECT_DIR
build-job:
stage: build
extends: [.go-cache]
script: |
make build
Expected behavior
I was expected for the cache mechanism to work but instead I have :
Error: Command failed with exit code 1: docker cp ec31163541291737df9d215d3d79ca1d06d3603ec5dd411bd9a52170d2712b5b:/cache/. .gitlab-ci-local/cache/.
mkdir /Users/user/git/helm-plugin/.gitlab-ci-local/cache/default/.go/pkg/mod/github.com/!burnt!sushi/[email protected]/.github: permission denied
at makeError (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Job.copyOut (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/src/job.ts:1019:13)
at /opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/src/job.ts:935:21
at Function.exclusive (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/src/mutex.ts:19:9)
at Job.copyCacheOut (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/src/job.ts:934:17)
at Job.start (/opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/src/job.ts:496:9)
at /opt/homebrew/Cellar/gitlab-ci-local/4.47.0/libexec/lib/node_modules/gitlab-ci-local/node_modules/p-map/index.js:57:22
Host information
macos
gitlab-ci-local 4.47.0
Containerd binary
I am using docker
Additional context
I've check the docker.io/firecow/gitlab-ci-local-util container and there is no volumes attached to it, despite this docker create