The container image is not pulled if already present. However, since the tag is latest, if I update it there is no way to update the runner with the new one.
In the meantime it would be cool if I could just add options: --pull always to the container section, but the option is not supported.
Hi, when running a job like this:
```yaml
jobs:
compile:
name: Compile
runs-on: ubuntu-latest
container:
image: myimage:latest
```
The container image is not pulled if already present. However, since the tag is `latest`, if I update it there is no way to update the runner with the new one.
GitHub also doesn't support this:
https://github.com/actions/runner/issues/791
https://github.com/actions/runner/issues/1713
I like the solution proposed here: https://github.com/actions/runner/issues/791#issuecomment-1572296966
In the meantime it would be cool if I could just add `options: --pull always` to the `container` section, but the option is not supported.
Faster way is to ssh to your act_runner host (if possible) and docker rmi <your_image>.
So in case somebody (like me) arrives here, I think if you are running the act_runner in nixos, you don't have this option.
(https://search.nixos.org/options?channel=23.05&sort=relevance&type=packages&query=gitea-actions-runner).
Faster way is to ssh to your act_runner host (if possible) and `docker rmi <your_image>`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi, when running a job like this:
The container image is not pulled if already present. However, since the tag is
latest, if I update it there is no way to update the runner with the new one.GitHub also doesn't support this:
https://github.com/actions/runner/issues/791
https://github.com/actions/runner/issues/1713
I like the solution proposed here: https://github.com/actions/runner/issues/791#issuecomment-1572296966
In the meantime it would be cool if I could just add
options: --pull alwaysto thecontainersection, but the option is not supported.Workaround: use the new ForcePull option on the yaml configuration
So in case somebody (like me) arrives here, I think if you are running the act_runner in nixos, you don't have this option.
(https://search.nixos.org/options?channel=23.05&sort=relevance&type=packages&query=gitea-actions-runner).
Faster way is to ssh to your act_runner host (if possible) and
docker rmi <your_image>.