fix: support "container.network: host" when using job services #1318
No reviewers
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner!1318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mfenniak/forgejo-runner:fix-networkmodehost-services"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Code archaeology here suggests that when services were first added to
act, the intent was to force a randomly named isolated network when services were present. Despite that intent, in runner v8.1.0 it was permitted to allow host networking to work when services were present. This regressed in8a8e01522dand currently neither behaviour works: a random network name is generated but not the network won't be created, causing an error in this configuration.This PR fixes the regression and adds a test verifying host networking and services can be used together. This configuration is in-use in the wild. Fixes #1310.