[GH-ISSUE #325] docker cp step fails with Python venv inside project directory #230

Closed
opened 2026-03-01 21:41:32 +03:00 by kerem · 2 comments
Owner

Originally created by @fhemberger on GitHub (Jul 31, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/325

I'm using direnv to automatically create a Python virtual environment inside my project directory. Trying to run act gives me the following issue:

act         
[test.yml/lint] 🚀  Start image=node:12.6-stretch-slim
[test.yml/lint]   🐳  docker run image=node:12.6-stretch-slim
                      entrypoint=["/usr/bin/tail" "-f" "/dev/null"]
                      cmd=[]
[test.yml/lint]   🐳  docker cp
                      src=/Users/frederic/my_project/.
                      dst=/github/workspace
Error: open /Users/frederic/Kunden/my_project/.direnv/python-venv-3.8.3/bin/python:
no such file or directory

Deleting/moving the virtual environment fixes the issue but breaks my project. 😉

This is related to issue #193 and PR #198, but instead of ignoring files in .gitignore, the solution here would be to respect the exclusion patterns in .gitignore instead.

It would be great to have a simple switch to enable/disable .gitignore, this would solve both issues.

Originally created by @fhemberger on GitHub (Jul 31, 2020). Original GitHub issue: https://github.com/nektos/act/issues/325 I'm using [direnv](https://github.com/direnv/direnv) to automatically create a [Python virtual environment](https://github.com/direnv/direnv/wiki/Python#venv-stdlib-module) inside my project directory. Trying to run `act` gives me the following issue: ``` act [test.yml/lint] 🚀 Start image=node:12.6-stretch-slim [test.yml/lint] 🐳 docker run image=node:12.6-stretch-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [test.yml/lint] 🐳 docker cp src=/Users/frederic/my_project/. dst=/github/workspace Error: open /Users/frederic/Kunden/my_project/.direnv/python-venv-3.8.3/bin/python: no such file or directory ``` Deleting/moving the virtual environment fixes the issue but breaks my project. 😉 This is related to issue #193 and PR #198, but instead of ignoring files in `.gitignore`, the solution here would be to respect the exclusion patterns in `.gitignore` instead. It would be great to have a simple switch to enable/disable `.gitignore`, this would solve both issues.
kerem 2026-03-01 21:41:32 +03:00
  • closed this issue
  • added the
    stale
    label
Author
Owner

@github-actions[bot] commented on GitHub (Sep 30, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:701064277 --> @github-actions[bot] commented on GitHub (Sep 30, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

@github-actions[bot] commented on GitHub (Jan 8, 2021):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:756474882 --> @github-actions[bot] commented on GitHub (Jan 8, 2021): Issue is stale and will be closed in 7 days unless there is new activity
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#230
No description provided.