Page History

Run the FrameworX runtime inside Docker with built-in HTTP probes for container orchestration-based deployments.

Reference → Runtime → Installation → Deployment → Docker

Version 10.1.5

+

Runtime Requirements

• .NET 10 runtime (the . The 10.1.5 runtime targets net10.0).
• Linux or Windows container host. Both official .NET 10 base images work.
• Writable volume for the solution folder, log folder, and Historian storage.
• Exposed TCP port for the runtime HTTP endpoint. The conventional port for the runtime service is 3101. Each service JSON sets its own portNumber.
• Network reachability to any connected PLCs, databases, MQTT brokers, and tRPC clients.

Image Layout

Place the runtime binaries under the container path /app/FactoryStudio and the solution under a mounted volume, for example /solutions/<SolutionName>. Log files go to /app/FactoryStudio/Logs.

.

The runtime exposes two probe endpoints on the same HTTP port as the main service. Both return a JSON body with snake_case fields.

Response Body — Healthy

{
  "status": "healthy",
  "version": "10.1.5.2010",
  "uptime_seconds": 3420,
  "solution": "Plant1",
  "started_at": "2026-04-19T13:22:10Z"
}
      

Response Body — Unhealthy

{
  "status": "unhealthy",
  "reason": "Kernel init failed",
  "version": "10.1.5.2010"
}
      

Status Values

The probe endpoints bypass the file-request block toggle. They answer even when IsFileRequestDisabled is set for the runtime HTTP server.

Dockerfile Example

FROM mcr.microsoft.com/dotnet/runtime:10.0

WORKDIR /app

COPY ./FactoryStudio /app/FactoryStudio
COPY ./Solution /solutions/Plant1

EXPOSE 3101

HEALTHCHECK --interval=10s --timeout=3s --start-period=30s --retries=3 \
  CMD curl --fail http://localhost:3101/health || exit 1

ENTRYPOINT ["dotnet", "/app/FactoryStudio/bin/net10.0/TStartup.dll", "/solution:/solutions/Plant1.tproj"]
      

Adjust the ENTRYPOINT to match the runtime service bundled in your image. The HEALTHCHECK directive lets Docker restart the container when the runtime reports unhealthy.

Kubernetes Manifest

Kubernetes maps the FrameworX probes to its liveness and readiness checksA minimal deployment manifest. A dedicated HTTP probe endpoint is planned for a later release. Until then, rely on Kubernetes process-liveness semantics and the Windows Service state on Windows nodes.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: frameworx-runtime
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: runtime
        image: tatsoft/frameworx-runtime:10.1.5
        ports:
        - containerPort: 3101
        readinessProbe:
          httpGet:
            path: /ready
            port: 3101
          initialDelaySeconds: 10
          periodSeconds: 5
        livenessProbe:
          httpGet:
            path: /health
            port: 3101
          initialDelaySeconds: 30
          periodSeconds: 15
          failureThreshold: 3
      

Persistent Volumes

Cloud Marketplace Images

Tatsoft publishes plans to publish prebuilt runtime images for Azure, AWS, and GCP marketplaces. Marketplace images ship with:

Images will ship with environment variables for the solution path, HTTP port, and license activation

, a default non-root user, and a minimal base image.

Point your orchestrator at the marketplace image tag for your target runtime version, mount a solution volume, and expose the HTTP port. No repackaging is required.

Troubleshooting

In this section...