Lambda native does not work if it has dependency on quarkus-resteasy

Describe the bug Following lambda guide works perfectly in native mode. But when adding dependency on io.quarkus:quarkus-resteasy it fails with java.lang.IllegalStateException: Failed to create cache dir at io.vertx.core.file.impl.FileResolver.setupCacheDir(FileResolver.java:332) at io.vertx.core.file.impl.FileResolver.<init>(FileResolver.java:87) at io.vertx.core.impl.VertxImpl.<init>(VertxImpl.java:165)

Found this (already fixed) bug that provided workaroud with forcing java.tmpdir to /tmp. Hovever the official 1.0.0.Final guide (and maven archetype) does not use additional sh bootstrap file, but simply renames native executable to bootstrap. On the side note, local invocation of lambda function with AWS SAM framework works without problem.

Expected behavior Guide and archetype should provide valid infrormation.

To Reproduce Steps to reproduce the behavior:

1. Create aws lambda project found here: https://quarkus.io/guides/amazon-lambda
2. Add extension quarkus-resteasy to the project and create a resteasy service within the code.
3. Build natively and upload to aws lambda.
4. execute lambda function

[louisbros]

I’m also facing this issue when using the quarkus-mailer with quarkus-amazon-lambda:

ERROR [io.qua.application] (main) Failed to start application: java.lang.IllegalStateException: Failed to create cache dir

Based on the information here, my solution was to:

1. Update the zip.xml to rename bootstrap to runner:

<file>
    <source>${project.build.directory}${file.separator}${artifactId}-${version}-runner</source>
    <outputDirectory>/</outputDirectory>
    <destName>runner</destName>
    <fileMode>755</fileMode>
</file>

1. Create a a new bootstrap.sh file to invoke the native runner with the java.io.tmpdir setting:

#!/bin/sh
./runner -Djava.io.tmpdir=/tmp

1. Modify the zip.xml file to include the new bootstrap file:

<file>
    <source>${project.basedir}/src/assembly/bootstrap.sh</source>
    <outputDirectory>/</outputDirectory>
    <destName>bootstrap</destName>
    <fileMode>755</fileMode>
</file>

[mihapolak]

@evanchooly , I agree with you to use amazon lambda http. But I guess there are other components using vertx? @mehdi-reza, local sam invoke shows /var/tmp/ (if not changed with custom bootstrap file), which obviously works within local tests but not in case of actual aws deployment.