As part of OFBIZ-12862, OFBIZ-12757, OFBIZ-12786 and OFBIZ-12798, docker deployments are being carried on VM ofbiz-vm1.apache.org for the demo-stable, demo-trunk and demo-next sites.
Work under OFBIZ-12757 also created 3 experimental sites:
These sites may be disabled at any time, but the hostnames will be left configured to enable rapid experimentation with demo sites in the future.
Files in this subdirectory of the ofbiz-tools repository reflect files which should be created on the root filesystem of ofbiz-vm1.apache.org with the following additions and/or settings:
At 02:35h UTC each day, the cronttab defined by /etc/cron.d/ofbizdocker will execute script pull-and-restart.sh.
The pull-and-restart.sh script does the following:
docker compose pull to pull the latest container images needed to support the docker compose application.docker compose down --volumes to shutdown and remove any existing containers and volumes for the docker compose application.docker compose up -d to start the containers for the docker compose application.New docker images are built and pushed to the GitHub Container Repository for each commit or tag on a branch. Depending on whether the build is triggered by a commit or a tag, the build will have ‘-snapshot’ appended to the image tag.
Any data that might have accumulated in the demo site is lost each time the refresh process is run as we also create a new database container for each site. One exception to deleting the data is that we do persist log files between refreshes, see framework/base/config/log4j2.xml for details. For access log files we use the Tomcat default format and there are rotable.
The demo-trunk application listens on AJP port 8009. The demo-stable application listens on AJP port 18009. The demo-next application listens on AJP port 28009.
If in use, the exp1 application listens on AJP port 38009, the exp2 application listens on AJP port 48009, and the exp3 application listens on AJP port 58009. The Apache server on ofbiz-vm1.apache.org has been configured to reverse-proxy to these applications for hostnames exp1.ofbiz.apache.org, exp2.ofbiz.apache.org and exp3.ofbiz.apache.org respectively.
The docker daemon on ofbiz-vm1.apache.org has been configured to use default user namespace remapping. This means that the UIDs of processes running within containers are mapped to a range of ‘high’ non-existing UIDs on the host system. Since the UIDs are non-existant, processes with those UIDs will have no priviledges on the host system.
See the dockremap entry in file /etc/subuid to see the range of UIDs that will be used for remapping.
A weekly cron job, /etc/cron.weekly/docker-system-prune, runs the docker system prune --force command to clean up unused container images.
For each demo instance (stable, next and trunk), the logs are respectively accessible under /home/ofbizdocker/[demo-stable|demo-next|demo-trunk]/logs