You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the --ephemeral runtime option isn't supported directly (it is via ${RUNNER_OPTIONS} I guess, but that doesn't change execution or deregistration of the runner.)
You appear to be emulating the ephemeral runner behavior here with the deregistration at the end of entrypoint.sh so just hard-code that into the ./config.sh line and remove the deregistration stuff. Probably don't need to run as a service, either; you can just have a bunch of UNSET lines which clean up the environment and call ./run.sh after configuration. The runner will exit after the job is complete, and the container will shut down, which appears to be the desired behavior. using set -i ./run.sh will fail, unfortunately, because some environment variables are needed.
This should do, I think. After adding --ephemeral to the ./config.sh line, replace everything after that command with this:
the
--ephemeral
runtime option isn't supported directly (it is via${RUNNER_OPTIONS}
I guess, but that doesn't change execution or deregistration of the runner.)You appear to be emulating the ephemeral runner behavior here with the deregistration at the end of
entrypoint.sh
so just hard-code that into the./config.sh
line and remove the deregistration stuff. Probably don't need to run as a service, either; you can just have a bunch ofUNSET
lines which clean up the environment and call./run.sh
after configuration. The runner will exit after the job is complete, and the container will shut down, which appears to be the desired behavior. usingset -i ./run.sh
will fail, unfortunately, because some environment variables are needed.This should do, I think. After adding
--ephemeral
to the./config.sh
line, replace everything after that command with this:The text was updated successfully, but these errors were encountered: