[GH-ISSUE #186] Folder is persisted across runs #124

Closed
opened 2026-03-01 21:40:25 +03:00 by kerem · 3 comments
Owner

Originally created by @Sygmei on GitHub (Apr 4, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/186

If I create a simple folder inside the cloned repository with the mkdir some_folder command and I try to re-run the script, it will fail with the following error :

mkdir: cannot create directory 'some_folder': File exists

Is this the expected behaviour ? Is there a way to clean the "cache" ?

Originally created by @Sygmei on GitHub (Apr 4, 2020). Original GitHub issue: https://github.com/nektos/act/issues/186 If I create a simple folder inside the cloned repository with the `mkdir some_folder` command and I try to re-run the script, it will fail with the following error : `mkdir: cannot create directory 'some_folder': File exists` Is this the expected behaviour ? Is there a way to clean the "cache" ?
kerem 2026-03-01 21:40:25 +03:00
Author
Owner

@chrislow commented on GitHub (Apr 4, 2020):

Got the same problem. There should be flag for clearing the cache / rebuild the image on every run?

<!-- gh-comment-id:609064553 --> @chrislow commented on GitHub (Apr 4, 2020): Got the same problem. There should be flag for clearing the cache / rebuild the image on every run?
Author
Owner

@cplee commented on GitHub (Apr 16, 2020):

there is a volume created for each job. it should get cleared after each job, but seems there may be situations in which the volume isn't being removed

<!-- gh-comment-id:614944862 --> @cplee commented on GitHub (Apr 16, 2020): there is a volume created for each job. it _should_ get cleared after each job, but seems there may be situations in which the volume isn't being removed
Author
Owner

@akx commented on GitHub (Jun 10, 2020):

Seeing the same thing here (act 0.2.9 from homebrew).

If it helps, it also looks like an orphan container is left running after the build (which failed for me).

<!-- gh-comment-id:641968656 --> @akx commented on GitHub (Jun 10, 2020): Seeing the same thing here (act 0.2.9 from homebrew). If it helps, it also looks like an orphan container is left running after the build (which failed for me).
Sign in to join this conversation.
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#124
No description provided.