[FOLIO-1941] SPIKE: Revisit approach to the FOLIO base Docker image Created: 04/Apr/19  Updated: 11/Aug/20  Resolved: 28/Nov/19

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

Type: Task Priority: P2
Reporter: John Malconian Assignee: Unassigned
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1544 switch to Alpine to shrink docker con... Closed
blocks UXPROD-1821 3rd party dependency upgrades (Q4 2019) Closed
blocks UXPROD-2214 3rd party dependency upgrades (Q1 2020) Closed
Relates
relates to FOLIO-1722 Update FOLIO Docker image: Alpine 3.1... Closed
relates to FOLIO-1772 Upgrade to OpenJDK 11 Closed
relates to FOLIO-1940 Update Jenkins docker build image Closed
Sprint: CP: ready for planning
Story Points: 3
Development Team: Core: Platform

 Description   

There are 2 FOLIO base docker images defined at https://github.com/folio-org/folio-tools/tree/master/folio-java-docker/openjdk8 :

  • folioci/openjdk8-jre based on Debian
  • folioci/openjdk8-jre-alpine based on Alpine

Both images have a startup script to run a jar file and have JMX + fabric8/agent-bond-agent tooling been added.
Much of it is outdated so now is a good time to decide what we want to include in the base image.



 Comments   
Comment by David Crossley [ 28/Nov/19 ]

Closed. This was subsequently handled by FOLIO-2358 Closed and FOLIO-2334 Closed .

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