[GH-ISSUE #1287] Add an option to Customize Container Name #697

New issue

Open

opened 2026-03-01 21:45:37 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 21:45:37 +03:00

Owner

Originally created by @PYPL-Song on GitHub (Jul 31, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1287

Act version

v0.2.29

Feature description

Error: failed to create container: Error response from daemon: Conflict. The container name "/act-Release-Extension-Release" is already in use by container "58ecf8e1eb8a796a8e5f737c43518f2e2a08e9d84cf31a9af7b32ee24b6c51a7". You have to remove (or rename) that container to be able to reuse that name.

I encountered this error when I try to build multiple tags at same time.
Can we have an option to specify the container name?

github.com/nektos/act@ddee19b946/pkg/model/planner.go (L39-L45)

github.com/nektos/act@ddee19b946/pkg/runner/run_context.go (L61)

Originally created by @PYPL-Song on GitHub (Jul 31, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1287 ### Act version v0.2.29 ### Feature description > Error: failed to create container: Error response from daemon: Conflict. The container name "/act-Release-Extension-Release" is already in use by container "58ecf8e1eb8a796a8e5f737c43518f2e2a08e9d84cf31a9af7b32ee24b6c51a7". You have to remove (or rename) that container to be able to reuse that name. I encountered this error when I try to build multiple tags at same time. Can we have an option to specify the container name? https://github.com/nektos/act/blob/ddee19b946bca0a168b2b1bcd5887d82557f2eac/pkg/model/planner.go#L39-L45 https://github.com/nektos/act/blob/ddee19b946bca0a168b2b1bcd5887d82557f2eac/pkg/runner/run_context.go#L61

kerem added the

kind/feature-request

label

2026-03-01 21:45:37 +03:00

kerem commented

2026-03-01 21:45:38 +03:00

Author

Owner

@phuhl commented on GitHub (Dec 11, 2023):

We have the same issue when using Act in our Jenkins-based CI. Running multiple instances of act in parallel does not work. The ability to add a unique string into the container name would fix the issue for us.

@phuhl commented on GitHub (Dec 11, 2023): We have the same issue when using Act in our Jenkins-based CI. Running multiple instances of act in parallel does not work. The ability to add a unique string into the container name would fix the issue for us.

kerem referenced this issue

2026-03-01 21:51:43 +03:00

[PR #698] [MERGED] feat: add option for custom socket path #1566

No milestone

No project

No assignees

1 participant

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

starred/act#697

No description provided.

Rows
Columns