gitea/act_runner
Fork 120
Code Issues 252 Pull Requests 13 Actions Releases 24 Activity

Allow job container to be attached to specific docker network #66

New Issue
Closed
opened 2023-03-21 23:47:01 +00:00 by sebthom · 1 comment
sebthom commented 2023-03-21 23:47:01 +00:00
Copy Link

As far as I understand network mode is currently hardcoded to "bridge".

I am not familiar with the act source code or even golang, but I think it is hardcoded here:

act_runner/runtime/task.go Line 81 in 48b05a0ca8
containerNetworkMode: "bridge", // TODO should be configurable

I am trying to use the runner in an environment where the job containers needs to be attached to a specific docker network to reach Gitea for e.g. SCM checkout etc.

As far as I understand network mode is currently hardcoded to "bridge". I am not familiar with the act source code or even golang, but I think it is hardcoded here: https://gitea.com/gitea/act_runner/src/commit/48b05a0ca8f3c1067bbdd88e83895edecccf1341/runtime/task.go#L81 I am trying to use the runner in an environment where the job containers needs to be attached to a specific docker network to reach Gitea for e.g. SCM checkout etc.
👍 1
wolfogre added the
kind
enhancement
 label 2023-04-04 03:57:24 +00:00
sebthom commented 2023-04-04 18:29:25 +00:00
Author
Copy Link

@wolfogre thanks!

@wolfogre thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
kind
bug
Something is not working
kind
build
kind/compatible
kind
dependencies
kind
docs
kind
enhancement
New feature
kind
feature
kind
help wanted
Need some help
kind
proposal
kind
refactor
related
act
Related to act.
related
environment
Related to the environment.
related
exec
related
gitea
Related to Gitea.
related
workflow
Related to the workflow file or actions scripts.
reviewed
confirmed
confirmed issue
reviewed
duplicate
This issue or pull request already exists
reviewed
invalid
Something is wrong
reviewed
needs feedback
reviewed
wontfix
This won't be fixed
reviewed
workaround
No Label
kind
enhancement
Milestone
No items
No Milestone
Assignees
Clear assignees
42wim 6543 a1012112796 Akkuman appleboy axifive betacat0 blumia bwko caicandong ChristopherHX davidsvantesson delvh denyskon fuxiaohei gary-kim garymoon giteabot guillep2k HesterG hiifong jaqra jolheiser jonasfranz jpraet kdumontnu kemzeb kerwin612 khmarbaise KN4CK3R kolaente lafriks lng2020 luhahn lunny mrsdizzie noerw puni9869 richmahn sapk screenshots sillyguodong silverwind smartclip_tim strk tboerger techknowlogick TheFox0x7 tobiasbp typeless volker.raschek wolfogre wxiaoguang yardenshoham yp05327 zeripath Zettat123
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/act_runner#66
Delete Branch "%!s()"

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?