Welcome to the new Linux Foundation Forum!

Lab 4 - rest-data-service app

cf push roster --no-manifest -i 1 -m 750m --random-route -b java-buildpack
I tried to push the app using the above command and it is giving following error

Updating app roster...
Mapping routes...
Comparing local files to remote cache...
All files found in remote cache; nothing to upload.
Waiting for API to complete processing files...

Staging app and tracing logs...
Cell d08d96df-321e-43e4-a1c9-a00503ec010b creating container for instance b0c7f800-902d-469b-a050-7cc48e44d1c0
Cell d08d96df-321e-43e4-a1c9-a00503ec010b successfully created container for instance b0c7f800-902d-469b-a050-7cc48e44d1c0
Downloading app package...
Downloaded app package (28M)
-----> Java Buildpack 3f4eee2 | https://github.com/cloudfoundry/java-buildpack.git#3f4eee2
[Buildpack] ERROR Finalize failed with exception #<RuntimeError: No container can run this application. Please ensure that you've pushed a valid JVM artifact or artifacts using the -p command line argument or path manifest entry. Information about valid JVM artifacts can be found at https://github.com/cloudfoundry/java-buildpack#additional-documentation. >
No container can run this application. Please ensure that you've pushed a valid JVM artifact or artifacts using the -p command line argument or path manifest entry. Information about valid JVM artifacts can be found at https://github.com/cloudfoundry/java-buildpack#additional-documentation.
Failed to compile droplet: Failed to run finalize script: exit status 1
Exit status 223
Cell d08d96df-321e-43e4-a1c9-a00503ec010b stopping instance b0c7f800-902d-469b-a050-7cc48e44d1c0
Cell d08d96df-321e-43e4-a1c9-a00503ec010b destroying container for instance b0c7f800-902d-469b-a050-7cc48e44d1c0
Cell d08d96df-321e-43e4-a1c9-a00503ec010b successfully destroyed container for instance b0c7f800-902d-469b-a050-7cc48e44d1c0
Error staging application: App staging failed in the buildpack compile phase
FAILED

Comments

  • spgreenbergspgreenberg Posts: 39

    You likely need to specify the path to the jar on your file system using the -p option. I do not see that in the command above.

Sign In or Register to comment.