Running XData Application as a Windows Service in a Docker Container (Windows Image)

BIZ TMS XData
1

We are developing an application using the TMS XData framework, and our goal is to deploy this application in a Docker container using a Windows base image.

The approach we are trying to follow is to register and start the XData application as a Windows Service inside the container, as this is the same methodology we already use successfully on our traditional Windows virtual machines (VMs).

The Problem:

When trying to replicate this process in the container environment, our XData service fails to start. The container builds and runs, but the service process either seems to not initialize or it terminates silently, without generating any logs or error messages.

To isolate the problem, we performed a control test: we created a basic Windows service using .NET. This test service, when configured in the exact same way in our Dockerfile, registers and starts correctly inside the container. This leads us to believe that our Docker environment and service installation process are correct, and that the issue is related to a specific particularity or dependency of the service compiled in Delphi with the XData framework when running in this containerized environment.

Our Questions:

We would like to request your guidance on the best practices for this scenario.

  1. Configuration as a Service: Are there any specific configurations, dependencies, or recommendations from TMS for running an XData application as a Windows Service inside a Windows container? Are there any container environment particularities that we should consider?
  2. Best Practice: Is this approach (Windows Service in a container) considered a best practice for deploying XData applications, or would you recommend an alternative?
  3. Suggested Alternative: For example, would it be more advisable to run the XData application as a console executable that keeps the container "alive" (a foreground process) instead of a background service? If so, what would be the best way to configure the XData project and the Dockerfile to manage the application's lifecycle in this scenario?

We thank you in advance for any documentation, examples, or recommendations you can provide to help us correctly configure the deployment of our XData application in a containerized Windows environment.

2

Not that we are currently aware of.

You have to take into account that a container is a completely new environment. I'd suggest that first you make sure your container is fit to run your XData code. Have you reserved the URL you are running the XData server, as you would have to do with any new computer you'd want to run a XData server?

First try to run the server as a console and log any exception you might find, as this is easier to find errors, especially those that happens at initialization time.

I'm not every experience in Windows containers, but I think that maybe since it's a container, you could simply start the server as a console application. The main points of using a service is to run unattended, without a logged user, with no need for manual launch from a restart, etc.. As far as I know all those issues are absent or at least minimized in a container setup, so running as a console makes it easier for you without losing the advantages.

Yep, I reached this part of your text after writing the above. So you already have your answer.