Running Hackolade CLI in Docker

This repository provides ready-to-use examples for the pre-built hackolade/hck-cli image: Hackolade Studio CLI, all target plugins, no build step.

All examples and compose files live under Studio/.

Writable paths — /data and /tmp (recommended)

The hackolade/hck-cli image steers runtime writes to /data and /tmp via XDG environment variables:

Path	Mount	Purpose
/data	Volume or PVC	License, logs, models, output, settings — everything that must persist
/tmp	tmpfs / memory emptyDir	Sockets, caches, scratch — everything ephemeral

Use these consolidated mounts in new deployments (all examples in this repo do). Older layouts under /home/hackolade/.config and /home/hackolade/Documents/* may still work on a writable root filesystem, but /data + /tmp is simpler and required for read-only rootfs / Kubernetes.

Details: Getting started — writable paths.

Documentation

Guide	When to use it
Getting started	First run — /data + /tmp mounts, deployment profiles, quick commands
Offline pipeline example	Full CI walkthrough — image upgrade, offline license, revEng → compMod → DDL → docs
Docker CLI how-to	docker run without Compose (local and hardened)
License validation	Online / offline floating license
Kubernetes	Restricted Pod Security Standard Jobs
Custom TLS certificates	Private CAs in hardened / K8s setups

cd Studio
docker compose -f compose.hardened.yml run --rm hck-cli

Legacy custom builds

Need a custom plugin set? Build on hackolade/studio — see getting-started.md.