search

cloudfoundry / docs-buildpacks

http://docs.cloudfoundry.org/buildpacks/
Apache License 2.0
21 stars 118 forks source link

https://stackoverflow.com/questions/59774751/spring-cloud-foundry-issue-223 #258

Closed javaHelper closed 4 years ago

javaHelper commented 4 years ago

Could you please guide https://stackoverflow.com/questions/59774751/spring-cloud-foundry-issue-223 ?

cf-gitbot commented 4 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

javaHelper commented 4 years ago

If you can quickly help us to fixed the issue, it will be great, we are really stuck with it. Kindly suggest what to use in manifest.yml file.

paigecalvert commented 4 years ago

Hi @javaHelper, sorry for the delay. Is this still something that we can help with? Can you elaborate on the issue you are having?

javaHelper commented 4 years ago

Its tooooo late to reply on this post.

I was getting error like below - 


Staging app and tracing logs...
   Downloading java_buildpack_offline...
   Downloaded java_buildpack_offline
   Cell 412efe1d-0e8c-4799-82e2-c57f58252812 creating container for instance fab4f527-2f6c-4408-9b9b-d3c343b0266a
   Cell 412efe1d-0e8c-4799-82e2-c57f58252812 successfully created container for instance fab4f527-2f6c-4408-9b9b-d3c343b0266a
   Downloading app package...
   Downloaded app package (164.3K)
   [1m[31m----->[0m[22m [1m[34mJava Buildpack[0m[22m [34mv4.26[0m [34m(offline)[0m | https://github.com/cloudfoundry/java-buildpack.git#e06e00b
   [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 412efe1d-0e8c-4799-82e2-c57f58252812 stopping instance fab4f527-2f6c-4408-9b9b-d3c343b0266a
   Cell 412efe1d-0e8c-4799-82e2-c57f58252812 destroying container for instance fab4f527-2f6c-4408-9b9b-d3c343b0266a
   Cell 412efe1d-0e8c-4799-82e2-c57f58252812 successfully destroyed container for instance fab4f527-2f6c-4408-9b9b-d3c343b0266a
Error staging application: App staging failed in the buildpack compile phase
FAILED

```java

Solution - 

As I was not extending the parent POM that need to manually add the repackage goal to make the fat jar with all the dependencies + make it executable. docs.spring.io/spring-boot/docs/current/maven-plugin/usage.html has an example. 

After adding the repackage goal per the docs and re-deploying the app
paigecalvert commented 4 years ago

I'm glad that you found a solution. For future issues, you can try reaching out to one of the CF mailing lists: https://lists.cloudfoundry.org/g/announce (This GitHub issue notifies the documentation team, and we are not always to most equip to answer these types of questions)