Suggested modification: use Azul OpenJDK and/or Tomcat 9 Docker containers

[unquietwiki]

Atlassian ships a copy of Tomcat 9 with their copies of Jira & Confluence, but it may be worth exploring stripping that out in favor of a Dockerized version. It also may be of interest to use the Azul Systems build of JDK, since they focus their activities on business support.

• https://hub.docker.com/r/amd64/tomcat/
• https://github.com/zulu-openjdk/zulu-openjdk
• https://cloakable.irdeto.com/2017/08/24/java-is-a-first-class-citizen-in-a-docker-ecosystem-now/

[blacklabelops]

Can you explain the benefits?

Tomcat and Java are included inside the Jira installation routine. It takes time, experience and effort to strip the java and tomcat installation routine.

Also it takes time and effort to maintain the tomcat configuration and compatible java version. Every release would have to be thoroughly tested before released.

[Firefishy]

I'd be strongly in favour of using the bundled JRE/JDK release that Atlassian ship with their releases.

[unquietwiki]

@blacklabelops @Firefishy Sorry I didn't reply sooner: been busy fighting with an instance of this & Confluence! 🗡

Reasoning for my suggestion....

• Atlassian only includes JDK as part of a bootstrap; they still expect you to use your own Java JDK, same as your own production database.
• Using RancherOS & Bitwarden have shown me that its possible to stack multiple containers together to create working systems. The former is a working Docker-hosting OS, based on Docker itself; the latter is a password-management system, that stacks Nginx, MS SQL Server for Linux, and PostgreSQL in a working distribution.
• Using containers to provide versioned software, allows for more granular control of the environment, per the 2nd point.

[blacklabelops]

to point (1)

Atlassian expects you to use a compatible JRE, example : https://confluence.atlassian.com/adminjiraserver070/supported-platforms-749382629.html

Your suggested JRE is not on this list. What's the benefit or motivation in your use to suggest this particular JRE?

to point (2)

This image supports "stack-wise" deployment. I have elaborated in the documentation how to use this image in combination with a mysql or postgres database and nginx reverse proxy.

What in particular are you missing in your use case?

to point (3)

blacklabelops/jira is the only image that uses the atlassian bundled jre. In the past this has been easier to maintain than blacklabelops/confluence that uses a containerized java jre. So blacklabelops/confluence already uses your approach.

[unquietwiki]

(1) I've used that particular build with other pieces of software, commercial & open-source, the past couple years now. They also offer commercial support to folks that need it, and sell their own fancier JVM. (2) I'm using GCE for deploying this & Confluence, with Container-Optimized OS. It's really meant to be used with one image at a time; but you can call additional images via startup-script commands (I'm not sure they self-restart though). (3) is meant more for your side, than mine. But it sounds like you're halfway there already, based on your other answers.

On Thu, Oct 18, 2018 at 3:05 AM Steffen Bleul notifications@github.com wrote:

to point (1)

Atlassian expects you to use a compatible JRE, example : https://confluence.atlassian.com/adminjiraserver070/supported-platforms-749382629.html

Your suggested JRE is not on this list. What's the benefit or motivation in your use to suggest this particular JRE?

to point (2)

This image supports "stack-wise" deployment. I have elaborated in the documentation how to use this image in combination with a mysql or postgres database and nginx reverse proxy.

What in particular are you missing in your use case?

to point (3)

blacklabelops/jira is the only image that uses the atlassian bundled jre. In the past this has been easier to maintain than blacklabelops/confluence that uses a containerized java jre. So blacklabelops/confluence already uses your approach.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blacklabelops/jira/issues/115#issuecomment-430951766, or mute the thread https://github.com/notifications/unsubscribe-auth/AA9fv8dVVm-tK0jhmbSYpIdsw6ZeuJWnks5umFJ5gaJpZM4XdlJ- .

--

Michael Adams https://unquietwiki.com/ http://www.unquietwiki.com/

[blacklabelops]

Thanks for your suggestion and opinion.

I will keep the bundled tomcat and jre because it's convenient and stable. When Atlassian stops bundling a java re then I will take a look at Zulu.

[unquietwiki]

(nods) Acknowledged. Thank you for hearing me out! And for putting this together.

On Thu, Oct 18, 2018, 11:15 PM Steffen Bleul notifications@github.com wrote:

Thanks for your suggestion and opinion.

I will keep the bundled tomcat and jre because it's convenient and stable. When Atlassian stops bundling a java re then I will take a look at Zulu.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blacklabelops/jira/issues/115#issuecomment-431256283, or mute the thread https://github.com/notifications/unsubscribe-auth/AA9fv35xNsDHDkwzYHus7Um3OuYh3wiPks5umW4TgaJpZM4XdlJ- .