Running DPE Nano Services in a container adds some additional IT-related complexity.
If you are new to DPE Nano Services, Linux or Containers we recommend to try out DPE Nano Services first under Windows, then under Linux and then finally inside a container.
Additional important links to read
Docker Images
Docker images are available on docker-registry-public.davidsystems.com:
-
docker-registry-public.davidsystems.com/dpe-nano-services:release2026.1.0 -
docker-registry-public.davidsystems.com/dpe-nano-services-alpine:release2026.1.0 -
docker-registry-public.davidsystems.com/dpe-contentmanager:release2026.1.0 -
docker-registry-public.davidsystems.com/dpe-admin:release2026.1.0
Please contact support to get credentials.
Example for a Docker Compose File
services:
nano-services:
container_name: dpe-nano-services-from-stack
image: docker-registry.davidsystems.com/dpe-nano-services:release2025.2.0
restart: always
ports:
- "17000:8080"
environment:
ASPNETCORE_ENVIRONMENT: Production
TZ: "Europe/Berlin"
DpeParFile__DIGASYSTEMREGISTRYXMLFILEPATH: /mnt/parfiles/DigaSystemRegistry_Linux.xml
DpeLogging__UseFileLogger: true
volumes:
- my_mount_to_parfiles:/mnt/parfiles
- /etc/my-feature-files-location-on-host:/app/Features
volumes:
my_mount_to_parfiles:
driver_opts:
type: cifs
o: username=dpedemo,password=MyPassword,rw,domain=david-gmbh.de
device: \\...ip_address...\DigaSystem
In this example
-
DPE licenses are injected into the containers /app/Features location from a host location
-
Parameters files are configured to be taken from a mounted volume
There are many other ways how to configure your container