Force java.io.tmpdir = /tmp for native executable #4327
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e to address vertx-cache folder creation problem
stuartwdouglas
approved these changes
Oct 2, 2019
|
Should this be done for the JVM part of the script as well? |
|
@cescoffier you were looking into this IIRC? |
|
@geoand yes it's a more general issue where we may have to pass the tmp directory in a lots of deployment. |
gsmet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The only writeable folder for Amazon Lambda is /tmp.
vert.x upon startup attempts to create [tmpdir]/vertx-cache, which for the native executable is pointing to a readonly folder (/var/tmp) and not /tmp.
By modifying the bootstrap script it will force the native executable to use the correct java.io.tmpdir=/tmp, and the vertx-cache folder can be created.