[GH-ISSUE #935 ] Issue: mkdir: cannot create directory &#39;/var/run/act/actions&#39;: Permission denied #552

Author

Owner

@catthehacker commented on GitHub (Dec 22, 2021):

Duplicate of #398

@catthehacker commented on GitHub (Dec 22, 2021): Duplicate of #398

kerem commented

Author

Owner

@bendizen commented on GitHub (Dec 22, 2021):

Downgrading to act 0.2.24 fixed it for me.

@bendizen commented on GitHub (Dec 22, 2021): Downgrading to act 0.2.24 fixed it for me.

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Jan 22, 2022):

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

@github-actions[bot] commented on GitHub (Jan 22, 2022): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@jessepinuelas commented on GitHub (Feb 9, 2022):

@catthehacker Still running into this error:
mkdir: cannot create directory '/var/run/act/actions': Permission denied

I added - run: sudo chown runner:docker /var/run/docker.sock to my steps in workflow am I missing something here?

@jessepinuelas commented on GitHub (Feb 9, 2022): @catthehacker **Still running into this error:** `mkdir: cannot create directory '/var/run/act/actions': Permission denied` I added - run: sudo chown runner:docker /var/run/docker.sock to my steps in workflow am I missing something here?

kerem commented

Author

Owner

@bendizen commented on GitHub (Feb 10, 2022):

@jessepinuelas this is how I downgraded it:

brew remove act
cd $(brew --repository)/Library/Taps/homebrew/homebrew-core/Formula
git checkout 3ab2604b1e630d4eccab40d0e78f29bd912a72b8 -- act.rb
brew install act
brew pin act
git checkout HEAD -- act.rb
act --version # make sure it's 0.2.24

@bendizen commented on GitHub (Feb 10, 2022): @jessepinuelas this is how I downgraded it: ``` brew remove act cd $(brew --repository)/Library/Taps/homebrew/homebrew-core/Formula git checkout 3ab2604b1e630d4eccab40d0e78f29bd912a72b8 -- act.rb brew install act brew pin act git checkout HEAD -- act.rb act --version # make sure it's 0.2.24 ```

kerem commented

Author

Owner

@agravelot commented on GitHub (Feb 17, 2022):

Adding --rebuild flag seems to fix the issue for me.

@agravelot commented on GitHub (Feb 17, 2022): Adding `--rebuild` flag seems to fix the issue for me.

kerem commented

Author

Owner

@mattjennings commented on GitHub (Feb 17, 2022):

--rebuild did not work for me, but downgrading to 0.2.24 per steps from @bendizen did.

@mattjennings commented on GitHub (Feb 17, 2022): `--rebuild` did not work for me, but downgrading to 0.2.24 per steps from @bendizen did.

kerem commented

Author

Owner

@drewyangdev commented on GitHub (Feb 24, 2022):

act version 0.2.25
Docker version 20.10.8, build 3967b7d
MacOS 12.2 3.1 GHz Dual-Core Intel Core i5

Didn't have any issue using the Medium image act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:act-latest at first, but later I need to use docker-compose which doesn't come with the Medium, so trying out with the Large image. The Large image act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:full-latest does come with docker-compose, but I'm having the same issue

[SV Functional Tests/test]   🐳  docker exec cmd=[mkdir -p /var/run/act/actions/browser-actions-setup-chrome@latest/] user= workdir=
| mkdir: cannot create directory '/var/run/act/actions': Permission denied

This issue isn't there by using the alternative Large image act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 , and docker-compose works as well. However, it's building super slow while running apt-get update.
I'll extend the Medium image by myself then...😭

@drewyangdev commented on GitHub (Feb 24, 2022): ``` act version 0.2.25 Docker version 20.10.8, build 3967b7d MacOS 12.2 3.1 GHz Dual-Core Intel Core i5 ``` - Didn't have any issue using the Medium image `act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:act-latest` at first, but later I need to use `docker-compose` which doesn't come with the Medium, so trying out with the Large image. The Large image `act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:full-latest` does come with `docker-compose`, but I'm having the same issue ``` [SV Functional Tests/test] 🐳 docker exec cmd=[mkdir -p /var/run/act/actions/browser-actions-setup-chrome@latest/] user= workdir= | mkdir: cannot create directory '/var/run/act/actions': Permission denied ``` - This issue isn't there by using the alternative Large image `act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04` , and `docker-compose` works as well. However, it's building super slow while running `apt-get update`. - I'll extend the Medium image by myself then...😭

kerem commented

Author

Owner

@Nuru commented on GitHub (Mar 10, 2022):

@catthehacker, what makes you think this is a duplicate of https://github.com/nektos/act/issues/398 ? The problem here is that somehow permissions on /var/run/act somehow go from

drwxrwxrwx 2 root root 4096 Mar  9 21:17 /var/run/act

drwxr-xr-x 3 root root 4096 Mar  9 21:19 /var/run/act

so that user cannot create /var/run/act/actions

The problem in 398 is that user is not root and not the user owning the files in the workdir.

@Nuru commented on GitHub (Mar 10, 2022): @catthehacker, what makes you think this is a duplicate of https://github.com/nektos/act/issues/398 ? The problem here is that somehow permissions on `/var/run/act` somehow go from ``` drwxrwxrwx 2 root root 4096 Mar 9 21:17 /var/run/act ``` to ``` drwxr-xr-x 3 root root 4096 Mar 9 21:19 /var/run/act ``` so that `user` cannot create `/var/run/act/actions` The problem in 398 is that `user` is not root and not the user owning the files in the workdir.

kerem commented

Author

Owner

@catthehacker commented on GitHub (Mar 10, 2022):

act currently doesn't support non-root users.

@catthehacker commented on GitHub (Mar 10, 2022): > `act` currently doesn't support non-root users.

kerem commented

Author

Owner

@ChristopherHX commented on GitHub (Mar 27, 2022):

I'm reopen this, because this problem is caused by github.com/nektos/act@c4db165d2d/cmd/root.go (L422) and the USER directive of these images.

act currently doesn't support non-root users.

No custom images are in use, you just need to select large in the first prompt of act to select an image.

Possible Workaround for act v0.2.25/26
Change the USER back to root of the large images.
You can alter the full images by creating a dockerfile and build the image
Dockerfile

FROM ghcr.io/catthehacker/ubuntu:full-20.04
USER 0

Then run docker build . -t ghcr.io/catthehacker/ubuntu:full-20.04, don't specify the -p, --pull option of act or the change is reverted.
Repeat it for all large image you want to use.

@ChristopherHX commented on GitHub (Mar 27, 2022): I'm reopen this, because this problem is caused by https://github.com/nektos/act/blob/c4db165d2d9b1abbddbe5516d0820bebbb5ebc83/cmd/root.go#L422 and the USER directive of these images. > act currently doesn't support non-root users. No custom images are in use, you just need to select large in the first prompt of act to select an image. Possible **Workaround** for act `v0.2.25`/`26` Change the USER back to root of the large images. You can alter the full images by creating a dockerfile and build the image Dockerfile ```Dockerfile FROM ghcr.io/catthehacker/ubuntu:full-20.04 USER 0 ``` Then run `docker build . -t ghcr.io/catthehacker/ubuntu:full-20.04`, don't specify the `-p, --pull` option of act or the change is reverted. Repeat it for all large image you want to use.

kerem commented

Author

Owner

@ahonnecke commented on GitHub (Apr 19, 2022):

@ChristopherHX I would very much like to be able to use this tool; I have this failure reproduced locally and would be happy to test a PR if and when one becomes available.

@ahonnecke commented on GitHub (Apr 19, 2022): @ChristopherHX I would very much like to be able to use this tool; I have this failure reproduced locally and would be happy to test a PR if and when one becomes available.

kerem commented

Author

Owner

@anoushk1234 commented on GitHub (May 6, 2022):

you must also unpin act otherwise it might not downgraded

@anoushk1234 commented on GitHub (May 6, 2022): you must also unpin act otherwise it might not downgraded

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Jun 6, 2022):

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

@github-actions[bot] commented on GitHub (Jun 6, 2022): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@Nuru commented on GitHub (Jun 6, 2022):

@ChristopherHX What is your current recommendation to work around this issue while waiting for a fix?

@Nuru commented on GitHub (Jun 6, 2022): @ChristopherHX What is your current recommendation to work around this issue while waiting for a fix?

kerem commented

Author

Owner

@ChristopherHX commented on GitHub (Jun 6, 2022):

What is your current recommendation to work around this issue while waiting for a fix?

Replace the user of the docker image with root ( uid 0 ): https://github.com/nektos/act/issues/935#issuecomment-1079940018

I saw new duplicated reports, this might really needs a fix in v0.2.27-dev.

This could be fixed by either

forcing the root user and ignore the user of the image
implementing non root user support https://github.com/nektos/act/issues/398
~~( This issue could be closed as duplicate, if the non root user is removed from the first time setup images. Requires fixes of .actrc or docker pull on all affected devices )~~

@ChristopherHX commented on GitHub (Jun 6, 2022): > What is your current recommendation to work around this issue while waiting for a fix? Replace the user of the docker image with root ( uid 0 ): https://github.com/nektos/act/issues/935#issuecomment-1079940018 I saw new duplicated reports, this might really needs a fix in v0.2.27-dev. This could be fixed by either - forcing the `root` user and ignore the user of the image - implementing non root user support https://github.com/nektos/act/issues/398 - ~~( This issue could be closed as duplicate, if the non root user is removed from the first time setup images. Requires fixes of .actrc or docker pull on all affected devices )~~

kerem commented

Author

Owner

@Ian1971 commented on GitHub (Jun 15, 2022):

what is curious for me is that I only get this if I do not have a checkout step or set the flag --no-skip-checkout. i.e. the fake checkout it does seems to get around this permission issue.

@Ian1971 commented on GitHub (Jun 15, 2022): what is curious for me is that I only get this if I do not have a checkout step or set the flag --no-skip-checkout. i.e. the fake checkout it does seems to get around this permission issue.

kerem commented

Author

Owner

@AdamSmithJuniperEducation commented on GitHub (Jun 15, 2022):

I was using the large size image and was recieving this error. I cleared out the ~/.actrc file and ran act again. I was presented with the select image size options. I selected medium and everything worked as expected.

@AdamSmithJuniperEducation commented on GitHub (Jun 15, 2022): I was using the large size image and was recieving this error. I cleared out the ~/.actrc file and ran act again. I was presented with the select image size options. I selected medium and everything worked as expected.

kerem commented

Author

Owner

@Ian1971 commented on GitHub (Jun 15, 2022):

hmmm ok, will give it a try. I switched to the large size image because something else wouldn't work (dotnet maybe)

@Ian1971 commented on GitHub (Jun 15, 2022): hmmm ok, will give it a try. I switched to the large size image because something else wouldn't work (dotnet maybe)

kerem commented

Author

Owner

@Ian1971 commented on GitHub (Jun 15, 2022):

So you are right the medium image doesn't have the permission issue. Sadly for me though that fails on actions/setup-dotnet@v2

@Ian1971 commented on GitHub (Jun 15, 2022): So you are right the medium image doesn't have the permission issue. Sadly for me though that fails on actions/setup-dotnet@v2

kerem commented

Author

Owner

@AdamSmithJuniperEducation commented on GitHub (Jun 16, 2022):

What error do you get @Ian1971? I am using setup-dontnet@v2 and it works fine. My snippet is below:

name: CI

on:
  push:
    branches: [ "*" ]
  pull_request:
    branches: [ "main" ]

env:
  SOLUTION_FILE: src/{#solution-file-name#}.sln

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Setup .NET Core SDK
        uses: actions/setup-dotnet@v2
        with:
          dotnet-version: 6.0.x
      - name: Build Solution
        run: dotnet build --configuration Release $SOLUTION_FILE
      - name: Run Tests
        run: dotnet test --no-restore --configuration Release $SOLUTION_FILE

@AdamSmithJuniperEducation commented on GitHub (Jun 16, 2022): What error do you get @Ian1971? I am using setup-dontnet@v2 and it works fine. My snippet is below: ``` name: CI on: push: branches: [ "*" ] pull_request: branches: [ "main" ] env: SOLUTION_FILE: src/{#solution-file-name#}.sln jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Setup .NET Core SDK uses: actions/setup-dotnet@v2 with: dotnet-version: 6.0.x - name: Build Solution run: dotnet build --configuration Release $SOLUTION_FILE - name: Run Tests run: dotnet test --no-restore --configuration Release $SOLUTION_FILE ```

kerem commented

Author

Owner

@Ian1971 commented on GitHub (Jun 16, 2022):

Ah actually it was a different step, I saw dotnet and assumed that was it. The error is actually this

    - uses: dotnet/nbgv@v0.4
      with:
        setAllVars: true     
        dotnet-version: ${{ inputs.netversion }}

(where ${{ inputs.netversion }}=6.0.x

[Build and Test/build_and_test]   â˜  git clone 'https://github.com/dotnet/nbgv' # ref=v0.4
[Build and Test/build_and_test]   ðŸ³  docker cp src=/home/ian/.cache/act/dotnet-nbgv@v0.4/ dst=/var/run/act/actions/dotnet-nbgv@v0.4/
[Build and Test/build_and_test]   ðŸ³  docker exec cmd=[mkdir -p /var/run/act/actions/dotnet-nbgv@v0.4/] user= workdir=
[Build and Test/build_and_test]   ðŸ³  docker exec cmd=[node /var/run/act/actions/dotnet-nbgv@v0.4/dist/index.js] user= workdir=
[Build and Test/build_and_test]   â—  ::error::Unable to locate executable file: dotnet. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
[Build and Test/build_and_test]   âŒ  Failure - dotnet/nbgv@v0.4

so I'll dig in to that action some more. Works on github though

@Ian1971 commented on GitHub (Jun 16, 2022): Ah actually it was a different step, I saw dotnet and assumed that was it. The error is actually this ``` - uses: dotnet/nbgv@v0.4 with: setAllVars: true dotnet-version: ${{ inputs.netversion }} ``` (where ${{ inputs.netversion }}=6.0.x ``` [Build and Test/build_and_test] â˜ git clone 'https://github.com/dotnet/nbgv' # ref=v0.4 [Build and Test/build_and_test] ðŸ³ docker cp src=/home/ian/.cache/act/dotnet-nbgv@v0.4/ dst=/var/run/act/actions/dotnet-nbgv@v0.4/ [Build and Test/build_and_test] ðŸ³ docker exec cmd=[mkdir -p /var/run/act/actions/dotnet-nbgv@v0.4/] user= workdir= [Build and Test/build_and_test] ðŸ³ docker exec cmd=[node /var/run/act/actions/dotnet-nbgv@v0.4/dist/index.js] user= workdir= [Build and Test/build_and_test] â— ::error::Unable to locate executable file: dotnet. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. [Build and Test/build_and_test] âŒ Failure - dotnet/nbgv@v0.4 ``` so I'll dig in to that action some more. Works on github though

kerem commented

Author

Owner

@AdamSmithJuniperEducation commented on GitHub (Jun 16, 2022):

Do you have the below in your steps with the appropriate .NET version before that step in your GitHub Workflow file?

      - name: Setup .NET Core SDK
        uses: actions/setup-dotnet@v2
        with:
          dotnet-version: 6.0.x

Looks like the step cannot find the dotnet SDK from the line ::error::Unable to locate executable file: dotnet. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

@AdamSmithJuniperEducation commented on GitHub (Jun 16, 2022): Do you have the below in your steps with the appropriate .NET version before that step in your GitHub Workflow file? ``` - name: Setup .NET Core SDK uses: actions/setup-dotnet@v2 with: dotnet-version: 6.0.x ``` Looks like the step cannot find the dotnet SDK from the line `::error::Unable to locate executable file: dotnet. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.`

kerem commented

Author

Owner

@Ian1971 commented on GitHub (Jun 16, 2022):

Yes it looks like this

    - name: Setup .NET
      uses: actions/setup-dotnet@v2
      with:
        dotnet-version: ${{ inputs.netversion }}
    - uses: dotnet/nbgv@v0.4
      with:
        setAllVars: true

@Ian1971 commented on GitHub (Jun 16, 2022): Yes it looks like this ``` - name: Setup .NET uses: actions/setup-dotnet@v2 with: dotnet-version: ${{ inputs.netversion }} - uses: dotnet/nbgv@v0.4 with: setAllVars: true ```

kerem commented

Author

Owner

@andylamp commented on GitHub (Jun 17, 2022):

The issue still exists in Ubuntu Linux hosts using act version 0.2.26...

@andylamp commented on GitHub (Jun 17, 2022): The issue still exists in Ubuntu Linux hosts using `act` version `0.2.26`...

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jun 17, 2022):

I re-pushed the images with default user being root

@catthehacker commented on GitHub (Jun 17, 2022): I re-pushed the images with default user being root

kerem commented

Author

Owner

@andylamp commented on GitHub (Jun 17, 2022):

@catthehacker - thanks! will try tomorrow and report back.

@andylamp commented on GitHub (Jun 17, 2022): @catthehacker - thanks! will try tomorrow and report back.

kerem commented

Author

Owner

@andylamp commented on GitHub (Jun 19, 2022):

The updated images seem to work as expected.

@andylamp commented on GitHub (Jun 19, 2022): The updated images seem to work as expected.

kerem commented

Author

Owner

@PhilippWillms commented on GitHub (Jul 31, 2022):

This issue is still occurring at my end. I am using the following:

Windows PowerShell 7.2
Running Windows Powershell in admin mode or non-admin mode does not change anything,
Act version == 0.2.29
Images: ghcr.io/catthehacker/ubuntu:act-latest

@PhilippWillms commented on GitHub (Jul 31, 2022): This issue is still occurring at my end. I am using the following: - Windows PowerShell 7.2 - Running Windows Powershell in admin mode or non-admin mode does not change anything, - Act version == 0.2.29 - Images: ghcr.io/catthehacker/ubuntu:act-latest

kerem commented