Java Buildpack staging error "status 223" when deploying a new Java Buildpack

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:
1. git clone https://github.com/cloudfoundry/java-buildpack 

2. bundle exec rake package OFFLINE=true version=v3.5.1

3. cf update-buildpack java_buildpack_df_offline -p java-buildpack-offline-26132cd.zip

From the CLI command line

> cf push cftest -p c:\local\Tools\sample.war -b java_buildpack_df_offline

..

..

Staging...
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223

FAILED
BuildpackCompileFailed 

Environment

Cause

After running the git clone https://github.com/cloudfoundry/java-buildpack, the resulting files may not contain the proper permissions.

A common reason for this *umask* value was 0027.

Resolution

In some cases, the environment "umask "settings are set to a more secure value such as "0027".

Ensure that "umask" value is set to "0022" to avoid this in the future. Otherwise, ensure the permissions are set as follows:

Good buildpack permissions

drwxr-xr-x 5 dfarrell staff 170 Mar 2 12:19 .
drwxr-xr-x 25 dfarrell staff 850 Mar 2 12:19 ..
-rwxr-xr-x 1 dfarrell staff 954 Mar 2 12:19 compile
-rwxr-xr-x 1 dfarrell staff 1099 Mar 2 12:19 detect
-rwxr-xr-x 1 dfarrell staff 976 Mar 2 12:19 release


Bad buildpack permissions

drwxr-x---@ 5 dfarrell staff 170 Feb 24 12:43 .
drwx------@ 7 dfarrell staff 238 Mar 2 15:02 ..
-rwxr-x---@ 1 dfarrell staff 954 Feb 24 12:43 compile
-rwxr-x---@ 1 dfarrell staff 1099 Feb 24 12:43 detect
-rwxr-x---@ 1 dfarrell staff 976 Feb 24 12:43 release 

The default installed JRE may not be Oracle. For example, if the user has OpenJDK installed, then the build pack could return this error when deploying the app. Refer to How to verify Java configuration, to determine what version of java is installed.