Skip to main content
Move stable setup out of repeated work. Record the immutable UUID produced by preparation and start later operations from that UUID.

Choose a preparation path

OCI import captures the filesystem root. Do not rely on OCI CMD, ENTRYPOINT, ports, health checks, or a service lifetime as the command for a later operation.

Python preparation

Complete Set up access. In a fresh project, run uv init --python 3.12 and uv add "contree-sdk==0.3.6". The fragments below run inside an async main(); Prepare once, reuse safely contains the complete entry point. With contree-sdk==0.3.6, run() prepares an awaitable request and execution begins when it is awaited:
A later read starts new compute:
Expected output:
Filesystem state survives only through a retained image. Processes, memory, services, and network connections do not.

Dockerfile and refresh rules

CLI 0.9.4 supports FROM, RUN, COPY/ADD, WORKDIR, ENV, ARG, and USER. Multi-stage AS is parsed but not executed. Each RUN is a Sandboxes operation; the client caches compatible layers. Use --no-cache for a deliberate full rebuild. Pin base images and dependencies, record the final UUID with the source revision, run a disposable smoke test, then move a shared tag. Keep registry credentials and build secrets outside uploaded files, retained environment values, and command output. See Build and refresh a reusable custom environment and Update images and clients.