forgejo/runner
31
88
Fork 91
Code Issues 38 Pull requests 9 Releases 81 Packages 1 Activity Actions 5

fix: kill containers explicitly, make Podman behave like Docker #1371

Merged
mfenniak merged 1 commit from aahlenst/runner:sigkill-containers into main 2026-02-12 16:38:30 +00:00
Conversation 2 Commits 1 Files changed 1 +12 -8
aahlenst commented 2026-02-12 13:49:02 +00:00
Member
Copy link

When Forgejo Runner is used with Podman, the "Complete job" step takes much longer than with Docker. The reason is that Podman and Docker behave differently when a container is removed that is still running. Podman tries to stop it first whereas Docker kills it outright. With this change, the container is killed explicitly before removing it. That aligns Podman's behaviour with Docker's. It makes the desired behaviour explicit, too.

  • bug fixes
    • PR: fix: kill containers explicitly, make Podman behave like Docker
When Forgejo Runner is used with Podman, the "Complete job" step takes much longer than with Docker. The reason is that Podman and Docker behave differently when a container is removed that is still running. Podman tries to stop it first whereas Docker kills it outright. With this change, the container is killed explicitly before removing it. That aligns Podman's behaviour with Docker's. It makes the desired behaviour explicit, too. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - bug fixes - [PR](https://code.forgejo.org/forgejo/runner/pulls/1371): <!--number 1371 --><!--line 0 --><!--description Zml4OiBraWxsIGNvbnRhaW5lcnMgZXhwbGljaXRseSwgbWFrZSBQb2RtYW4gYmVoYXZlIGxpa2UgRG9ja2Vy-->fix: kill containers explicitly, make Podman behave like Docker<!--description--> <!--end release-notes-assistant-->
fix: kill containers explicitly, make Podman behave like Docker
All checks were successful
checks / validate pre-commit-hooks file (pull_request) Successful in 35s
Details
checks / Build Forgejo Runner (pull_request) Successful in 40s
Details
checks / validate mocks (pull_request) Successful in 43s
Details
checks / Build unsupported platforms (pull_request) Successful in 17s
Details
checks / runner exec tests (pull_request) Successful in 26s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 9m13s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 11m1s
Details
issue-labels / release-notes (pull_request_target) Successful in 3s
Details
cascade / debug (pull_request_target) Has been skipped
Details
cascade / end-to-end (pull_request_target) Successful in 6s
Details
cascade / forgejo (pull_request_target) Successful in 1m11s
Details
0409263545
mfenniak approved these changes 2026-02-12 16:03:00 +00:00
cascading-pr commented 2026-02-12 16:03:17 +00:00
Contributor
Copy link

cascading-pr updated at actions/setup-forgejo#883

cascading-pr updated at https://code.forgejo.org/actions/setup-forgejo/pulls/883
Sign in to join this conversation.
Reviewers
No reviewers
mfenniak
Labels
Clear labels   
FreeBSD

   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Chore

It is no fun but it needs to be done, this is a chore.

  
Kind/DependencyUpdate

for pull requests that are created by renovate when updating a dependency

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Windows

Windows ports is an independent project, see https://github.com/Crown0815/Forgejo-runner-windows-builder

  
linux-powerpc64le

powerpc64le

  
linux-riscv64

   
linux-s390x

   
run-end-to-end-tests

Run https://code.forgejo.org/forgejo/end-to-end with a runner compiled from this pull request

  
run-forgejo-tests

Run https://codeberg.org/forgejo/forgejo tests importing the runner from this pull request

No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/runner!1371
No description provided.