Another attempt to fix the GITEA_RUNNER_GID envar issue. See
https://github.com/vegardit/docker-gitea-act-runner/issues/5
Tested this GITEA_RUNNER_GID envar fix without building the
upstream image, as that was problematic to achieve locally.
The fixed image requires either compose: 'user:root' OR
restart: always (or unless-stopped). Why? The UID change in
/opt/run.sh fails the first time, at its next sudo command.
Basically: changing the running UID's /etc/passwd entry causes
the 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.
Signed-off-by: William Blew <william@kulian.org>
image/run.sh fails to the container:act user's effective GID to the
GITEA_RUNNER_GID envar's value due due to a 'usermod -o -u'
typo. It should be: usermod -o -g "$GITEA_RUNNER_GID" act
Signed-off-by: William Blew <william@kulian.org>
William Blew
sebthom
Jake Howard