-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
PermissionError: [Errno 13] Permission denied: 'Deployment.md' #374
Comments
BTW, using the image |
It seems to crash when trying to delete the ./compiled folder |
As a quick (and very dirty) solution we could just use root inside the docker images instead of the kapitan user. Otherwise anyone running the Image and mounting a kapitan project directory will have to make sure user "1000" has permissions on it which seems implausible. :/ |
I made #375 to add yq to the docker images. |
locally it works fine, confirmed. the issue was only on cloud build |
How about we turn this into a `kapitan_docker.sh` shell script which we'll
test and maintain?
…On Tue, Sep 17, 2019 at 5:09 PM ademariag ***@***.***> wrote:
locally it works fine, confirmed. the issue was only on cloud build
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#374>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEFAAGKT34CWULOW76KKTLQKD6M3ANCNFSM4IXMXFIA>
.
|
I will try this again with the -u flag. |
I am still having issues with this. Am I the only one using kapitan with cloud build? cloudbuild.yml
error
|
The issue goes away if I use the |
Won't fix I guess. On cloud build the image to use is the CI one. |
Describe the bug/feature
We are experiencing a problem with Cloud Build and the latest version of Kapitan (latest)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Build fails with
[Errno 13] Permission denied: 'Deployment.md'
Screenshots
** If it's a bug (please complete the following information):**
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: