Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: GITHUB_ENV is not guaranteed to exist, causes a permission denied error #729

Closed
blampe opened this issue Jun 8, 2021 · 0 comments · Fixed by #726
Closed

Issue: GITHUB_ENV is not guaranteed to exist, causes a permission denied error #729

blampe opened this issue Jun 8, 2021 · 0 comments · Fixed by #726
Labels
kind/bug Something isn't working meta/resolved Issue has been fixed or valid solution has been provided (not workaround)

Comments

@blampe
Copy link

blampe commented Jun 8, 2021

Upgraded act while trying to debug another issue and ran into this bug which broke a step which was working fine on 0.21.

System information

  • Operating System: Darwin Kernel Version 20.5.0
  • Architecture: x86_64
  • Apple M1: No
  • Docker version: 20.10.6, build 370c289
  • Docker image used in act: catthehacker/ubuntu:full-20.04
  • act version: 05bce00

Expected behaviour

Runs successfully.

Actual behaviour

[Foo/foo-2] Exec command '[node /var/run/act/actions/aws-actions-configure-aws-credentials@v1/dist/index.js]'
[Foo/foo-1]   ❗  ::error::EACCES: permission denied, open '/var/run/act/workflow/envs.txt'
[Rails Tests/rails_tests-1]   ❌  Failure - Configure AWS Credentials

Workflow and/or repository

name: Foo
jobs:
  foo:
    steps:
      - uses: aws-actions/configure-aws-credentials@v1
@blampe blampe added the kind/bug Something isn't working label Jun 8, 2021
@cplee cplee closed this as completed in #726 Jun 9, 2021
@catthehacker catthehacker added the meta/resolved Issue has been fixed or valid solution has been provided (not workaround) label Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working meta/resolved Issue has been fixed or valid solution has been provided (not workaround)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants