Disable/move default webapps, per upstream recommendation#181
Disable/move default webapps, per upstream recommendation#181yosifkit merged 1 commit intodocker-library:masterfrom
Conversation
|
Note: if you are currently using any of these default webapps, this is a BREAKING CHANGE (intentionally). They are still available within the image under |
Instead of relying on existing example applets (docker-library/tomcat#181), this loads a very simple `index.jsp` file into the Tomcat webapps and verifies that it gets executed correctly.
Instead of relying on existing example applets (docker-library/tomcat#181), this loads a very simple `index.jsp` file into the Tomcat webapps and verifies that it gets executed correctly.
|
Thanks to docker-library/official-images#7217 this is now green. 👍 As an example of one easy way to restore some default example webapp (such as the FROM tomcat:9.0-jdk13-openjdk-oracle
RUN cp -avT $CATALINA_HOME/webapps.dist/manager $CATALINA_HOME/webapps/managerA symlink would probably work as well, although that's untested. |
Changes: - docker-library/tomcat@151e932: Merge pull request docker-library/tomcat#181 from infosiftr/webapps - docker-library/tomcat@807a2b4: Disable/move default webapps, per upstream recommendation
As of docker-library/tomcat#181, the upstream-provided (example) webapps are not enabled by default.
|
For those looking to use the stock image and add manager back in you can do with with an altered entrypoint. Handy alternative to building a custom image just to have the manager. |
See https://tomcat.apache.org/tomcat-9.0-doc/security-howto.html#Default_web_applications
Closes #124