Compose applications

Compose is available for multi-service applications and supporting data services. A Compose document is always configuration with deployment authority: review it as carefully as application code.

AI-generated drafts

The AI assistant produces a draft. It does not bypass authorization or admission policy. Before creation, Autodisc rejects AI-generated Compose that requests:

• arbitrary build directives;
• missing, variable-controlled, or latest image tags;
• privileged containers;
• host network, PID, or IPC namespaces;
• host devices or added Linux capabilities;
• unconfined security profiles;
• host bind mounts or the Docker socket;
• directly published host ports;
• absolute or traversal-based generated config-file paths.

A safe draft uses pinned images, internal container ports, named volumes, and explicit domains managed by the platform.

Review before creation

Confirm the services, images, environment variable names, persistent volumes, domains, and expected memory before creating a stack. Secrets should be generated or entered through the platform, not accepted blindly from model output.

Server ownership still applies

Compose services on shared capacity remain tenant-scoped. Raw host Docker and Swarm controls are available only on dedicated, attached, or operator-owned infrastructure.