fail to launch quarkus dev with gettings-started Gradle project on Ubuntu

[zmila]

Hello.
Due to SNYK vulnerability complaints, we're migrating our project from Quarkus 3.15.1 to latest 3.18.3. I had some problems with the rest-client library and to find the root cause I tried to bootstrap a new empty project. Following https://quarkus.io/guides/getting-started.
I do

~/prg/java/qua/qua_3.18$ quarkus create app org.acme:getting-started --extension='rest' --gradle
-----------
selected extensions: 
- io.quarkus:quarkus-rest


applying codestarts...
📚 java
🔨 gradle
📦 quarkus
📝 config-properties
🔧 tooling-dockerfiles
🔧 tooling-gradle-wrapper
🚀 rest-codestart

-----------
[SUCCESS] ✅  quarkus project has been successfully generated in:
--> ..../prg/java/qua/qua_3.18/getting-started
-----------
Navigate into this directory and get started: quarkus dev

~/prg/java/qua/qua_3.18$ cd getting-started/
~/prg/java/qua/qua_3.18/getting-started$ ls
build.gradle  gradle  gradle.properties  gradlew  gradlew.bat  README.md  settings.gradle  src

~/prg/java/qua/qua_3.18/getting-started$ quarkus dev
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
Gradle could not start your build.
> Cannot create service of type BuildSessionActionExecutor using method LauncherServices$ToolingBuildSessionScopeServices.createActionExecutor() as there is a problem with parameter #22 of type ValueSnapshotter.
   > Cannot create service of type ValueSnapshotter using method WorkerSharedBuildSessionScopeServices.createValueSnapshotter() as there is a problem with parameter #1 of type List<ValueSnapshotterSerializerRegistry>.
      > Could not create service of type BuildLifecycleAwareVirtualFileSystem using GradleUserHomeServices.createVirtualFileSystem().
         > Failed to initialise native integration.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 1s

~/prg/java/qua/qua_3.18/getting-started$ quarkus --version
3.18.3

~/prg/java/qua/qua_3.18/getting-started$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.5 LTS
Release:	22.04
Codename:	jammy

~/prg/java/qua/qua_3.18/getting-started$ ./gradlew --version

------------------------------------------------------------
Gradle 8.12
------------------------------------------------------------

Build time:    2024-12-20 15:46:53 UTC
Revision:      a3cacb207fec727859be9354c1937da2e59004c1

Kotlin:        2.0.21
Groovy:        3.0.22
Ant:           Apache Ant(TM) version 1.10.15 compiled on August 25 2024
Launcher JVM:  17.0.14 (Eclipse Adoptium 17.0.14+7)
Daemon JVM:    /usr/lib/jvm/temurin-17-jdk-amd64 (no JDK specified, using current Java home)
OS:            Linux 6.8.0-53-generic amd64

The same command without --gradle creates a maven project that I can successfully build and run.

Existing project where I just updated the version in settings file:

quarkusPluginVersion=3.18.3
quarkusPlatformGroupId=io.quarkus.platform
quarkusPlatformArtifactId=quarkus-bom
quarkusPlatformVersion=3.18.3

Is building and running ok too.

Something is wrong with empty projects bootstrapped with "create app --gradle" or "--gradle-kotlin-dsl".

[quarkus-bot[bot]]

/cc @geoand (kotlin), @glefloch, @quarkusio/devtools

[geoand]

I just tried this and it worked just fine, so I don't know what to tell you here

[zmila]

No problem.

Further investigations show, that this is most probably a Gradle problem.
gradle/gradle#31946
"... the error happens when the tmp partition is mounted with noexec flag."