quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Contributor’s guide

7. Containers and runtime ownership

The Dockerfile uses a pinned Ubuntu builder and the local Triglav-OS docker-dotnet:latest runtime. C++ release/debug executables link their C++ and compiler runtimes statically while retaining the glibc runtime contract. The runtime stage contains binaries and license notices, not source or credentials. The .NET application is published separately into its own small runtime context.

The root Compose project runs cloud and CoreDNS with private state/leaf mounts, non-root ownership, dropped capabilities and loopback host publication. The Azure listener is reachable on private-network port 443. CoreDNS mounts only the generated DNS directory; it does not read the identity or secret stores.

application-env.py owns a separate application environment: unique test projects or a persistent development project, matching CA/DNS/client settings, the separate engine supervisor and cleanup constrained to owned resources. Client trust is mounted as public certificates, not installed into the host. The application image has a runtime; interactive SDK development uses another container as described in the user book.

Native engines are not child processes in the cloud container. Only the explicit supervisor has Docker-administrator access. Requests cannot choose arbitrary images, mounts, commands or Docker flags. Container/volume labels identify the supervisor's runtime and each instance for safe reconciliation and deletion.

The optional telemetry image starts only Collector, Grafana, Prometheus, Loki and Tempo through an explicit launcher. It is digest-pinned, drops capabilities, uses a read-only root and bounded resources, and exposes only loopback HTTPS ports. Grafana requires authentication. Health probes check the actual five services, not the upstream launcher's marker files. Tool data persists separately.

See container operations (source checkout required), application ownership (source checkout required), engine runtime (source checkout required) and telemetry operations (source checkout required).