Closed g-farrow closed 3 years ago
Hi @g-farrow,
Thank you for reporting this. I havent had an opportunity to reproduce yet, but someone will take a look when they have an opportunity. We have marked this issue as a p2
, this means it may be some time before it gets addressed. If you think this should be a higher priority, feel free to get upvotes and we will escalate.
If you need this done more quickly than we can offer, please feel free to submit a PR with a fix.
😸 😷
Hi @NGL321
It looks like this is not a CDK issue - but actually, an issue caused by a change to the GitHub Action's base image: https://github.com/youyo/aws-cdk-github-actions/issues/36
Therefore I'm going to close this issue - thanks!
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
I had this issue, however, I don't believe the issue to be a problem in CDK.
If you're running a CDK deploy within a container on Github Actions, then there's a mismatch between the user inside the Docker container, and the permissions of the __w
directory.
The issue is described at https://github.com/actions/runner/issues/1203
A workaround and issue to track is at https://github.com/actions/runner/issues/691
In case it disappears, I've extracted the workaround:
jobs:
configure:
runs-on: ubuntu-latest
outputs:
uid_gid: ${{ steps.get-user.outputs.uid_gid }}
steps:
- id: get-user
run: echo "::set-output name=uid_gid::$(id -u):$(id -g)"
clone-and-install:
needs: configure
runs-on: ubuntu-latest
container:
image: mcr.microsoft.com/vscode/devcontainers/base:ubuntu
options: --user ${{ needs.configure.outputs.uid_gid }}
steps:
- uses: actions/checkout@v2
When running a cdk deploy in GitHub Actions I have started to get the following error:
Error: EACCES: permission denied, mkdir.
This error occurs since upgrading from
v1.102.0
tov1.1.9.0
Reproduction Steps
package.json
dependencies:GitHub Actions config:
What did you expect to happen?
CDK will deploy as it did before I upgraded
What actually happened?
Failed with an error trying to create a directory
Environment
Other
This is :bug: Bug Report