Create a GPU Container Job in the web interface
Get shell access to whole GPUs by creating a GPU Container Job in the CosmicAC web interface.
Create a GPU Container Job to get shell access to one or more whole GPUs. The form has six sections, Job type, Basics, Source, Hardware, Notifications, and Review, and Continue takes you from one to the next. For a description of every field, see the Job configuration reference.
Prerequisites
You need the following before you start:
- A running CosmicAC deployment. See Installation.
- Access to the CosmicAC web interface.
Steps
Open the new job form
In the left navigation, click Jobs, then click New Job.
Select the job type
In the What kind of job? section, select GPU Container, then click Continue.
Enter the basics
In the Basics section, enter a Job name and add at least one tag in Tags. To add a tag, type it, then press Enter.
Click Continue.
Select the base image and disk
In the Image & access section, select a Base OS image. For Disk (GB), select a preset or enter a value.
Click Continue.
Select the hardware
In the Hardware section, select a Location first. The GPU list stays empty until you select one.
Select a GPU from the ones available in that location, where each card shows the GPU's VRAM, CPU, and RAM. Set the GPU count, then set the CUDA / driver. Below the count, Available GPUs is the number of free GPUs in that location.
Click Continue.
Select the notification events
In the Notifications section, turn on each job lifecycle event you want this job to report. CosmicAC turns all four on by default.
- job.failed: the job transitions to Failed, and the event carries the failure reason.
- job.degraded: healthy replicas drop below the count you set, and the endpoint stays live.
- job.recovered: the job returns to Active from Degraded or Failed.
- job.restart_storm: any replica restarts three times within 10 minutes.
These preferences cover this job alone. An event you turn on here reaches your webhook only if it's also turned on in Settings → Notifications, which also controls the model health and usage window events for the whole deployment. See Set up webhook notifications.
Click Continue.
Review and create the job
In the Review & launch section, check that it reports Ready to create, then click Create job. If it reports issues instead, click Edit on the row that names the problem, fix it, then return to this section.
Open a shell on the job
The job appears on the Jobs page. Wait for its status to reach Running. To open an interactive shell on it, see Access a GPU Container Job.
Help and troubleshooting
Job stuck in Creating or Starting
If a job stays in Creating or Starting, check the status of its KubeVirt virtual machine instance (VMI).
-
Find the job's container ID. Click Jobs in the left navigation, and then click the job. The Containers section lists the Container ID for each container.
-
Find the VMI for the container.
CosmicAC creates one VMI for each container and names it
<container-id>-n0. A multi-node job has one VMI per node.From a machine with
kubectlaccess to your Kubernetes cluster, run:kubectl get vmi -n <namespace>Replace
<namespace>with the namespace configured inK8S_NAMESPACE. -
Check the VMI status:
-
If the VMI is not Running, inspect its events:
kubectl describe vmi <container-id>-n0 -n <namespace> -
If the VMI is Running but the job stays in Creating or Starting, cosmicac-wrk-agent-instance cannot reach cosmicac-wrk-server-k8s-nvidia. These two components connect directly, and some cluster network configurations can block the connection.
To route the connection through a relay, see Set up a relay for CosmicAC.
-