Run images and Dockerfile builds safely.
Docker applications run a public or private OCI image, or build an image from a repository Dockerfile. They use the same files, logs, domains, process metrics, and lifecycle views as other ServerChirp applications.
Provide an image reference and, for a private image, choose encrypted registry credentials. Before deployment, ServerChirp can inspect the image digest, architecture, operating system, size, entrypoint, command, user, workdir, exposed ports, environment keys, healthcheck, and labels.
Choose a repository, build context, and Dockerfile path. A successful build produces an immutable image revision associated with the source commit. Deployment history keeps the requested image, resolved digest, architecture, pull or build time, activation time, and failure details.
Override the entrypoint, argv, working directory, container user, interactivity, and environment when the image defaults are not sufficient.
Resource controls include memory, CPU, swap, out-of-memory behavior, restart policy, restart window, and stop timeout.
Persistent mounts attach named files or directories and may be read-only. Published ports support TCP or UDP, a selected bind address, and conflict-free host-port allocation.
For HTTP traffic, select one primary container port and publish it through managed Nginx with a preview or custom domain and SSL. Direct TCP or UDP exposure creates the corresponding managed firewall rule.
ServerChirp starts a candidate container instance before marking its revision active and records its process state, exit code, and readiness timestamps. Retained revisions make it possible to reactivate a previous known image, but mounted or external data changes still require a separate recovery plan.
