Hey!
I’m faced with the challenge of deploying FME Remote Engine Services in a hybride cloud scenario. In this scenario, Windows/Linux VMs are not an option and I came up with the idea of packaging RES in a Ubuntu-based Docker Image for a containerized deployment. (Question: FME Remote Engine Services - How to build Docker Image and Container? | SafeSoftware Community)
My approach was to use silent install with a cfg-file like officially supported for FME Flow installation on a Ubuntu base image. However, I’m adapting it for the Remote Engine Services, which are shipped as a *.run file. This works, however, there is no official support for Remote Engine Services as Docker or Kubernetes deployment and as a workaround I had to build my custom Docker image.
It seems like a low hangig fruit to provide official support for Docker and Kubernetes not only for FME Flow but also FME Remote Engine Services. Looking at (hybride) cloud deployments getting more important, I think having Remote Engine Services officially available for Kubernetes/Docker would help a lot of uses cases which aim to bring FME computing closer to cloud data and applications...