gitlab-ci-local: Error while using gitlab-ci-local within podman

Currenty we are switching from docker in docker to podman in out pipeline. Since we are not allowed to have priviledged access in our gitlab runners, we need the podman functionality.

Currently we are running into this error message:

Error: Command failed with exit code 1: docker run --rm -v gcl-versioningOgcommon-44494-tmp:/tmp/ -v gcl-versioningOgcommon-44494-build:/app/ firecow/gitlab-ci-local-util bash -c chown 0:0 -R /app/ && chmod a+rw -R /app/ && chmod a+rw -R /tmp/
   unable to upgrade to tcp, received 409
       at makeError (/usr/local/lib/node_modules/gitlab-ci-local/node_modules/execa/lib/error.js:60:11)
       at handlePromise (/usr/local/lib/node_modules/gitlab-ci-local/node_modules/execa/index.js:118:26)
       at processTicksAndRejections (node:internal/process/task_queues:95:5)
       at Job.execScripts (/usr/local/lib/node_modules/gitlab-ci-local/src/job.ts:624:13)
       at Job.start (/usr/local/lib/node_modules/gitlab-ci-local/src/job.ts:367:36)

Do you know if that is a common issue that we need to fix on our side or is it a specific issue?

Assumption

I think it might have something to do with missing priviledges while creating containers from within podman. It would be great if you could elaborate why priviledged access is needed at all. It seems it is only needed to set folder rights.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (7 by maintainers)

Most upvoted comments

I release/publish every now and then 😁