Integrate (product engineers)
Containers and Kubernetes
Keep a stable fingerprint when your product runs in Docker or Kubernetes.
Containers are rebuilt and rescheduled all the time. The fingerprint must survive that, or each restart looks like a new machine and uses another seat.
How the installation ID is resolved
PORTCULLIS_INSTALLATION_IDenvironment variable, if set (recommended for Kubernetes and Docker).<dataDir>/installation-id, a random UUID created on first run.dataDirmust be a persistent volume.- The OS machine ID, only if your product explicitly chooses that strategy. Not recommended in containers.
With (2), the ID survives restarts and container rebuilds as long as the volume persists. A cloned volume shows up to Digicom as the same fingerprint on a different host, rather than a silent copy.
What to put in your install guide
Tell operators to:
- mount the product's data directory on a persistent volume (Docker volume or Kubernetes
persistent volume claim), because it holds
installation-id,license.licandlicense.state; - optionally set
PORTCULLIS_INSTALLATION_IDto a fixed value per installation (for example a UUID in the Helm values or compose file); - allow outbound HTTPS to the Portcullis API host for online installations.
Everything that presents the same installation ID for the same product has the same fingerprint, and Portcullis treats it as one machine.
Docker Compose
services:
omnifleet:
image: <your-product-image>
environment:
PORTCULLIS_INSTALLATION_ID: "3f0b6a0e-6a52-4c1e-9a55-1d2f8f0c7b11"
volumes:
- omnifleet-data:/var/lib/omnifleet # the product's data directory
volumes:
omnifleet-data:Kubernetes
env:
- name: PORTCULLIS_INSTALLATION_ID
value: "3f0b6a0e-6a52-4c1e-9a55-1d2f8f0c7b11"
volumeMounts:
- name: data
mountPath: /var/lib/omnifleet # the product's data directory
volumes:
- name: data
persistentVolumeClaim:
claimName: omnifleet-dataThe paths and image names above are examples; use your product's real data directory.