Provide a Docker image for deploying the XWiki instance

This is a meta-task about providing the correct Docker image needed to deploy the XWiki instance autonomously within the Phoenix environment.

On a high level, we need to have the following features for ensuring this deployment :

• Have the XWiki configuration files updated dynamically through environment variables that are passed to the docker container
• Have the container use the WAR that we build as part of this project

added Deployment Infrastructure labels

assigned to @caubin

Added some tests as part of https://git.xwikisas.com/xwikisas/phoenix/xwiki-docker/-/commit/a1cb72a43dd528befadafbaa342bc040366246ef

assigned to @gsautner and unassigned @caubin

Assigning to @gsautner for now. Guilherme already worked on the first item of this task as part of his improvements on the XWiki Helm chart (have a way to customize the contents of xwiki.properties and xwiki.cfg through variables).

For the next steps, we'll need to see how to integrate a way to build the docker image of this project directly as part of the build.

changed milestone to %SWP - Milestone 3

mentioned in commit 7ee24744

mentioned in commit 49f58a10

mentioned in commit 67758a0b

mentioned in commit ee0cc870

mentioned in commit c53f99f6

mentioned in commit 3544d8db

mentioned in commit 61d82b2c

About tests using jib maven plugin to create SWP xwiki image.

Using this plugin we can create Docker images during maven build phases, which enable us to always uptodate image versions from source or have automated releases during maven release.

To test this, branch testing-jib-plugin was created to receive changes.

To create this new type “distribution”, 2 new modules were created (docker-mariadb and docker-mysql). We can create later for postgres too.

This modules are copy from war module, with this differences:

• Have src/main with custom docker-entrypoint and hibernate.cfg files.
• Ignore “deploy” in this extra war modules
• Always run jib build to always update container images on CI/pipelines executions.
• Image with same name of project with tag name: ${project.version}-(mysql|mariadb)-tomcat

On first tests, the default (official) xwiki docker image as base to only append new layers, but this approach create very huge (1.6GB) image since layers are not in good order to this kind of “extension”.

In order get better image size, changed template on xwiki-docker to have the follow targets and layer order:

1. FROM tomcat:9.0.69-jr11 AS base-tomcat

… all current default actions (install tools/libreoffice, env. scripts volume etc.)

1. FROM base-tomcat AS xwiki

… layers with xwiki war/settings

1. FROM xwiki AS xwiki-database

… layer fixing database lib and settings

And using only base-tomcat target on jib plugin as 'from' image, final image have similar size of official one (1.2G)

In order to test on local env.without changing maven version, one layer was added to this image with all extensions present on xip distribution.

To move this preloaded extensions to correct the data directory a new line was added on docker-entrypoint. Nice of this, is have support for more fast startup and maybe a “offiline” support.

Changes made on this project, only wait for pipelines run that container registry will be updated.

To change something in base docker image, change needs to be done on this project/branch XWiki Docker - testing-newbuildorder

gradlew generate
cd 14\mariadb 
docker build -t git.xwikisas.com:5050/xwikisas/swp/xwiki-docker:14-base-tomcat --target base-tomcat .
docker push git.xwikisas.com:5050/xwikisas/swp/xwiki-docker:14-base-tomcat 

mentioned in commit 827aabd6

mentioned in merge request !1 (merged)

changed title from Provide a Docker image for depolying the XWiki instance to Provide a Docker image for deploying the XWiki instance

mentioned in commit 5f11e9d8

mentioned in commit 2fffef29