[FOLIO-2740] Use Okapi container in single-server reference builds Created: 19/Aug/20  Updated: 08/Sep/20

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

Type: Task Priority: TBD
Reporter: Wayne Schneider Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-2737 Update Vagrant builds to use Ubuntu F... Closed
relates to FOLIO-2730 New Jenkins release pipeline for Okap... Closed
Sprint:
Development Team: FOLIO DevOps

 Description   

Currently all our single-server reference builds use the Okapi Debian package to install Okapi. This obviously creates dependency issues for Okapi based on the host OS. If we move to using a container for Okapi, we have a more portable reference build solution.

The last time we tried this, there were issues with communication between Okapi running in a container and the local Docker control plane, which Okapi needs access to in order to deploy modules.

The idea would be to create a new role in folio-ansible for deploying Okapi as a container, and transition the reference builds to using that. We would also transition the "single server" install documentation in folio-install to use a container instead of the Debian package.


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