-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Use unsecure entropy source in docker packaging tests #119598
Use unsecure entropy source in docker packaging tests #119598
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -112,6 +115,13 @@ String build() { | |||
// Limit container memory | |||
cmd.add("--memory " + memory); | |||
|
|||
// Add default java opts | |||
if (this.envVars.containsKey("CLI_JAVA_OPTS")) { | |||
this.envVars.put("CLI_JAVA_OPTS", this.envVars.get("CLI_JAVA_OPTS") + " " + DEFAULT_JAVA_OPTS); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use this with ES_JAVA_OPTS as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use this with ES_JAVA_OPTS as well?
We could. It doesn't affect this particular issue as security auto config is done in the CLI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and added it on the chance we add anything else to DEFAULT_JAVA_OPTS
.
While investigating #119441 thread dumps indicate container startup hung up in security auto-configuration generating certificates. This is likely due to a low source of entropy during these tests as they run serially so there is little other activity on the host machine. This change configures ES to use
/dev/urandom
as the entropy source, which while less secure, should alleviate the problem.