-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Custom actions ignores container volumes #9409
Comments
We have the same problem. Any news from the team? |
Same here |
I have the same issue. Is there an easy and clean fix? |
Same here. |
Same issue here. Why is the FYI @cglenn36 Edit: Right now we have no workaround for this...I am going to try to see if I can debug what's going on here. From what we've seen, it looks like it does parse and validate the overrides, but they just never actually get overlayed in the resulting manifest for some reason. |
…s from job manifest Fixes GoogleContainerTools#9409
In case anyone is watching, I have a PR open with a proposed fix, just working on tests and awaiting feedback. But in case anyone can't wait the fix is pretty simple, and it eliminates the need for using the |
When I run the custom action my container settings in my job manifest are overridden by the container specification in the custom actions. When I use the
overrides
keyword it does not seem to apply these overrides to the final yaml file.Expected behavior
That the container mounts the volumes.
Actual behavior
The volume mounts are overridden and ignored.
Information
Similar issue: #8974
Job.yaml
Steps to reproduce the behavior
Setup a volume mount for the container in a custom actions.
Run the custom action - no volume is mounted.
The text was updated successfully, but these errors were encountered: