[FOLIO-1889] SPIKE: Find new source for Java 8 for Vagrant builds Created: 22/Mar/19  Updated: 03/Jun/20  Resolved: 22/Mar/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P1
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1897 Upgrade Docker in reference environments Open
relates to FOLIO-1896 Change Vagrant image base to bento/ub... Closed
relates to FOLIO-1772 Upgrade to OpenJDK 11 Closed
relates to FOLIO-1589 Replace Oracle JDK 8 by January 2019 Closed
Sprint: Core: Platform - Sprint 59
Story Points: 3
Development Team: Core: Platform

 Description   

Debian Jessie is the current basis for the Vagrant boxes. It does not have support for OpenJDK 8, except through backports. Jessie backports were announced as end of life in July, 2018 (https://lists.debian.org/debian-backports-announce/2018/07/msg00000.html), and they have been removed from the Debian apt repository as of March 21, 2019.

With this change, no Vagrant boxes can be built.



 Comments   
Comment by Wayne Schneider [ 22/Mar/19 ]

Other possible solutions:

  • Move to Ubuntu LTS
  • Use Okapi in a container
  • Install Java 8 from sdkman.io
  • Find another backport for Java 8
Comment by Adam Dickmeiss [ 22/Mar/19 ]

Suddenly FOLIO-1772 Closed became more important

Comment by Jakub Skoczen [ 22/Mar/19 ]

Wayne Schneider can you elaborate on the solution with running Okapi in a container?

Comment by Wayne Schneider [ 22/Mar/19 ]

Okapi is currently run in our reference environments using the released Debian package, which runs the fat JAR using the system Java. We could instead use the released container of Okapi. It would take some testing to get the configuration right, of course.

Comment by John Malconian [ 22/Mar/19 ]

Ubuntu 18 LTS might be the easiest path here.

Comment by Julian Ladisch [ 22/Mar/19 ]

The Vagrant boxes are also used as reference development environments where a developer should be able to build any back-end module.
See https://folio-org.atlassian.net/browse/FOLIO-1772 about version11 incompatibilities: For example aspectj-maven-plugin (used in RMB) is not yet version 11 compliant.

Comment by Wayne Schneider [ 22/Mar/19 ]

steve.osguthorpe also suggests looking at https://aws.amazon.com/corretto/

Comment by Wayne Schneider [ 22/Mar/19 ]

Thanks, all, for the input. I think the best path forward short term is to change the base Vagrant image for our Vagrant boxes to either Debian Stretch (maintenance support through June 2024), Ubuntu 16.04 (maintenance support through April 2021) or Ubuntu 18.04 (maintenance support through April 2023) – all of which offer OpenJDK-based Java 8 as a package in their main repos. Other sources for Java 8 (SDKMAN, AdoptOpenJDK, Amazon Corretto) would make automated installation considerably more complicated (though not impossible, of course). Feel free to comment further on the issue if you have other questions or concerns.

Comment by Wayne Schneider [ 22/Mar/19 ]

Debian Stretch has a challenge of too small a root partition in the base Vagrant image (we had the same challenge with Jessie, had to make an awkward workaround), testing now with Ubuntu 18.04. We know Ubuntu 16.04 will work, as that is the current reference platform on AWS.

Comment by Wayne Schneider [ 22/Mar/19 ]

Conclusion: the best short term solution is to change the base image to Ubuntu 16.04, as Ubuntu 18.04 does not work with the older docker-engine packages we are using. Created FOLIO-1896 Closed as an issue to resolve immediately, FOLIO-1897 Open to capture the less urgent task of upgrading Docker.

Generated at Thu Feb 08 23:16:38 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.