# Build A Python Web Container From Den This tutorial builds a Python web application container from the local Den OCI base image. It is the most practical starter path for application teams: build Den as a base image, then put the application in a normal container layer. This does not boot Den as a VM and it does not run systemd. The container uses the Den rootfs userland and conda runtime that `ct run oci-image` packages from the staged Den image. ## Build The Den Base Image From the Den checkout: ```bash ct run oci-image ``` This creates: ```text den:dev ``` ## Build The Application Container Build the example image: ```bash docker build \ --platform linux/arm64 \ -t den-python-web-example:local \ examples/oci/python-web ``` Use `--platform linux/amd64` instead when `den:dev` was built from the `linux-64` Den target. The example Dockerfile starts from `den:dev`, creates a conda environment under `/opt/app`, installs FastAPI and Uvicorn from `conda-forge`, and copies the application into `/srv/den-python-web/`. ## Run It Start the container: ```bash docker run --rm -p 8080:8080 den-python-web-example:local ``` Check the health endpoint: ```bash curl http://127.0.0.1:8080/healthz ``` The response should include: ```json { "status": "ok" } ``` ## What This Proves This proves that Den can act as a conda-native OCI base image for application containers. It does not prove that a booted Den VM can run Docker or Podman as a container host. That requires a container runtime package, kernel and cgroup configuration, and a dedicated smoke test.