The GITEA_RUNNER_GID envar, another attempt.
wblew opened this issue · comments
Follow-up to closed Issue #5
That issue's PR #6 is broken. The resulting image will not start when the GITEA_RUNNER_GID is present and not 1000.
That is because my testing was inadequate, related to being unable to build the vegardit/gitea-act-runner image locally.
Method of testing: I used the attached the attached docker-compose.yml and Dockerfile.test in the root of this repo.
It does work, despite the container having to restart, due to sudo failure at
docker-gitea-act-runner/image/run.sh
Line 48 in 4c9806d
Basically: changing the running UID's /etc/passwd entry causes its next sudo command to fail.
The container restart (without wiping the read/write layer) starts with the already changed /etc/passwd, and then continues without the sudo error.
Created PR #10 that fixes this issue.
Here is the docker compose log from my testing. Note the 1st execution failure, and the subsequent success.