Zenika / alpine-chrome

Chrome Headless docker images built upon alpine official image
https://hub.docker.com/r/zenika/alpine-chrome
Apache License 2.0
1.85k stars 243 forks source link

GCP Cloud Build: EACCES: permission denied, mkdir '/workspace/node_modules' #181

Open xuanswe opened 3 years ago

xuanswe commented 3 years ago

Describe the bug

I have this error on GCP Cloud Build:

error Could not write file "/workspace/yarn-error.log": "EACCES: permission denied, open '/workspace/yarn-error.log'"
error An unexpected error occurred: "EACCES: permission denied, mkdir '/workspace/node_modules'".

To Reproduce Steps to reproduce the behavior:

  1. cloudbuild.yaml
steps:
  - name: zenika/alpine-chrome:89-with-node-14
    dir: '/usr/src/app'
    entrypoint: yarn
    args: [ 'install' ]
  1. Run the build on GCP Cloud Build, I got error message:
error Could not write file "/workspace/yarn-error.log": "EACCES: permission denied, open '/workspace/yarn-error.log'"
error An unexpected error occurred: "EACCES: permission denied, mkdir '/workspace/node_modules'".
  1. If now, I change cloudbuild.yaml as below:
steps:
  - name: node:14
    entrypoint: yarn
    args: [ 'install' ]
  - name: zenika/alpine-chrome:89-with-node-14
    entrypoint: yarn
    args: [ 'test' ]
  1. The first step works, but 2nd step has new error message:
Step #1: Error: EACCES: permission denied, open '/builder/home/.config/yarn'
Step #1:     at Object.openSync (fs.js:476:3)
Step #1:     at readFileSync (fs.js:377:35)
Step #1:     at /usr/share/node_modules/yarn/lib/cli.js:101332:58
Step #1:     at Array.map (<anonymous>)
Step #1:     at parseRcPaths (/usr/share/node_modules/yarn/lib/cli.js:101330:78)
Step #1:     at Object.findRc (/usr/share/node_modules/yarn/lib/cli.js:101344:10)
Step #1:     at getRcConfigForCwd (/usr/share/node_modules/yarn/lib/cli.js:56916:74)
Step #1:     at /usr/share/node_modules/yarn/lib/cli.js:92695:56
Step #1:     at Generator.next (<anonymous>)
Step #1:     at step (/usr/share/node_modules/yarn/lib/cli.js:310:30)

Additional context Running locally with Docker for Windows on my machine, everything is fine.

a-stankevich commented 1 year ago

I observe the same issue. Have you been able to find a solution?