-
Notifications
You must be signed in to change notification settings - Fork 80
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated README Changed tomcat image to tomcat:7.0.108-jdk8-openjdk-buster due to no upstream support for tomcat:7-jre8-alpine
- Loading branch information
Showing
4 changed files
with
54 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2becaf6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There actually is an image
tomcat:7-jre8-alpine
and alsotomcat:9-jre8-alpine
. Also, they are smaller than the Debian-based images by manifolds. Is there a specific reason why you would not use them anymore? We are currently using the Alpine-based images at one of our projects and it works well. Also, the immense memory saving actually makes a real difference for our build server.2becaf6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As indicated in the commit message, the primary issue with those images is that they haven't been updated in a couple years (i.e. "no upstream support"), as you can see here for 9-jre8-alpine. I don't know why they stopped building (or at least pushing) them, but we need to use something that's more up to date in terms of security and performance updates in both Java environment and Tomcat. It looks as if none of the x-jre8-y images are being updated either, so it's possible that a fair amount of the size overhead between those images is due to JRE vs JDK.