Earl Warren 773bb92aa3 fix: container removal is the runner responsibility (#851) ... If a container is configured for implicit removal in the docker/podman server, it will race against the explicit removal performed by the runner. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - bug fixes - [PR](https://code.forgejo.org/forgejo/runner/pulls/851): <!--number 851 --><!--line 0 --><!--description Zml4OiBjb250YWluZXIgcmVtb3ZhbCBpcyB0aGUgcnVubmVyIHJlc3BvbnNpYmlsaXR5-->fix: container removal is the runner responsibility<!--description--> <!--end release-notes-assistant--> Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/851 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>		2025-08-14 07:47:50 +00:00
..
logging.go	Cherry-pick gitea act_runner #543	2024-11-03 13:57:34 +00:00
runner.go	fix: container removal is the runner responsibility (#851)	2025-08-14 07:47:50 +00:00
runner_test.go	chore: to allow the runner to be imported, v9 needs to be in the go module (#777)	2025-07-31 10:35:11 +00:00
workflow.go	chore: to allow the runner to be imported, v9 needs to be in the go module (#777)	2025-07-31 10:35:11 +00:00
workflow_test.go	chore: to allow the runner to be imported, v9 needs to be in the go module (#777)	2025-07-31 10:35:11 +00:00