You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if the workspace directory and/or any other volume defined in the step were mapped directly, but it could also be a good option to accept volumes as parameters with the -v option. Something like
The text was updated successfully, but these errors were encountered:
jkevingutierrez
changed the title
Can't write files into workspace folder in Cloud Build
Can't write files into /workspace folder in Cloud Build
Sep 7, 2021
jkevingutierrez
changed the title
Can't write files into /workspace folder in Cloud Build
exec-wrapper Can't write files into /workspace folder in Cloud Build
Sep 7, 2021
jkevingutierrez
changed the title
exec-wrapper Can't write files into /workspace folder in Cloud Build
exec-wrapper can't write files into /workspace folder in Cloud Build
Sep 7, 2021
Trying to run a Cloud Build file like the next:
Is throwing an error, as it can't write in the
/workspace
folder:touch: cannot touch '/workspace/test.txt': Permission denied
It would be great if the workspace directory and/or any other volume defined in the step were mapped directly, but it could also be a good option to accept volumes as parameters with the
-v
option. Something likeThe text was updated successfully, but these errors were encountered: