Java deploy fails: Gradle is unavailable in the build environment
Error recorded 3 times in PanelAlpha Engine deploys on Java. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen3 times
WhereJava
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The deployment detected the Java/Gradle strategy, but the application contains a Maven project descriptor and the build environment does not provide a gradle command. The build container also cannot write to /root, indicating an incorrect home-directory or volume permission mapping. Either issue can stop the application before startup.
What the log looks like
Deploy log
Detected project type: Java (Gradle)Using strategy: javaLoaded base image maven:3-eclipse-temurin-21 from host cacheCompiling application on hostmkdir: cannot create directory ‘/root’: Permission deniedCan not write to /root/.m2/copy_reference_file.log. Wrong volume permissions? Carrying on ...sh: 1: gradle: not foundDeploy failed: Failed to start app