CRI Management

Vapor can interact directly with the host's Container Runtime Interface (CRI) socket (e.g., /run/containerd/containerd.sock). This is particularly useful for debugging Kubernetes nodes or running containers without the Docker daemon.

Managing CRI Workloads

Navigate to Containers > CRI.

The interface provides similar capabilities to the Docker view but operates directly against the CRI:

• Images: Pull or import OCI-compliant container images. Like Docker, Vapor supports TUS-based resumable uploads for large image archives.
• Containers: View the raw containers running under the CRI. Note that in a Kubernetes environment, these containers are typically managed by the kubelet, and modifying them manually here should be done with caution.
• Logs & Exec: View logs and open terminal sessions into CRI containers for low-level debugging.