libQt5Core.so.5: cannot open shared object file: No such file or directory

Symptom

When deploying FME Server using containers (Docker or Kubernetes) on a CentOS 7 or RHEL host, the FME Server Engine containers will fail to start.

The following error will be seen in the container logs: 

/opt/fme-engine-2021/bin/fme: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

Cause

This is due to a kernel mismatch between the Ubuntu 20.04 libraries used when building the FME Server engine container, and the kernel version on CentOS 7 and RHEL.

Resolution

To resolve this issue, FME Server engine containers will now be built on a CentOS 7 image, in addition to the Ubuntu engine images (default).
 

Docker

To use the CentOS 7 engine images in your compose file, add the centos7 tag to your engine image:

fmeserverenginestandard_1:
    image: 'quay.io/safesoftware/fmeserver-engine:21326-centos7'

You can find the supported engines by browsing Docker Hub, and looking at the engine tags.
 

Kubernetes

The helm chart changes to support CentOS 7 containers are in the 2021.1 release helm chart, so you must use that version of the helm chart. You can specify the correct engine tag in the values.yaml file like this:

fmeserver:
  image:
    tag: 21326
  engines:
  - name: "standard-group"
    engines: 2
    image:
      tag: 21326-centos7