-
Notifications
You must be signed in to change notification settings - Fork 528
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
env attribute does not work when a "-" is present #718
Comments
So the way the error is reporting it seems docker itself is mistaking the "-" as a docker flag, not as part of the environment variable. As I don't see any parameters in your string, maybe simplify it with single quotes just to be sure it's not passing something odd? so:
Otherwise I agree: what you're passing should work. |
Thanks for the quick response. I have tried single quotes but get the same result. I agree it seems like docker is interpreting the value incorrectly, but when I run the command that puppet is sending to stdout directly it works. That command again is:
I wonder if what puppet is printing to stdout is actually different to what it is running? |
Any updates on this issue ? Even I am facing the same problem. |
I just had this same issue and have tried all sorts of escaping of the options (single quotes, double quotes, escaped double quotes, etc.). I'm not sure if this issue is actually tied to this puppet module though, or rather tied to systemd trying to run docker with the flags, since if you grab what's being put in the systemd file and run it manually, it works. For now, I've gone with overriding the entire jvm.options file in docker instead of passing the environment variable, but it's not ideal. |
I am trying to start an elasticsearch container using the below piece of code. The issue I am having is with setting a JVM environment variable on the env attribute.
The above code yields the following result:
As a test, if I pass in only a JVM param for the initial heap space (above), I get the following:
Seems maybe there is an issue with how the value of env is transformed? However puppet logs show the below, which looks OK...
At this point i'm not really sure how to proceed and thinking maybe this is a bug?
The text was updated successfully, but these errors were encountered: