application.home_IS_UNDEFINED
See original GitHub issueThere are error logs in default configuration, not being able to open the log file. After extending my compose:
command: ["-Dpidfile.path=/dev/null", "-Dapplication.home=/kafka-manager"]
the home is set properly and log files are found. Both parameters should probably be predefined in Dockerfile so we don’t have to override in run/compose…
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Why catalina.home_IS_UNDEFINED directory is generated by ...
I have written logback configuration file for my application, but when I was doing maven clean install(mvn clean install), it generated a ...
Read more >app.home_IS_UNDEFINED folder when deploying via WAR ...
When using Studio to generate a WAR file and a logback configuration file, a folder called “app.home_IS_UNDEFINED” is created in the ROOT ...
Read more >gitea: 20.03: After upgrade to 11.8: html/template: "home" is ...
I guess the problem is caused by overwriting systemd.services.gitea.serviceConfig . This causes that app.ini is not reconstructed and so the ...
Read more >undefinedundefined
Try our Learning Management System for free. mCourser supports online schools, free courses, real-time evaluation, private classes and more...
Read more >Patrol for Oracle Weblogic Application Server (Weblogic KM ...
After installation of Oracle Weblogic KM getting WL_HOME and JAVA_HOME is undefined or inaccessible in SRP_startClient.*.log.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
From a few test runs it seems to build in 1 retry so 5 is probably more than enough. I’ll make a pull request once I have everything ready. I guess the failure is either unstable longstanding connections or rate limiting in certain repos.
I tried several things.
I seperated the source download run so the build failure preserves the layer at least. Then I followed the suggestion you linked but added build in a while loop instead of multiple RUN commands. This now nicely restarts the build on failure. I think I need to add a retry counter at least just in case so it doesn’t build in infinity for a broken version.
https://github.com/cen1/kafka-manager-docker/tree/feature/robustBuilds