Submit a Run:AI job for execution
runai submit job-name [--always-pull-image] [--args stringArray] [--backoffLimit int] [--command stringArray] [--completions int] [--cpu double] [--cpu-limit double] [--elastic] [--environment stringArray | -e stringArray] [--gpu int | -g int] [--host-ipc] [--host-network] [--image string | -i string] [--interactive] [--jupyter] [--large-shm] [--local-image] [--memory string] [--memory-limit string] [--node-type string] [--parallelism int] [--port stringArray] [--preemptible] [--prevent-privilege-escalation] [--pvc [StorageClassName]:Size:ContainerMountPath:[ro]] [--run-as-user] [--service-type string | -s string] [--template string] [--ttl-after-finish duration] [--volume stringArray | -v stringArray] [--working-dir] . [--loglevel string] [--project string | -p string] [--help | -h]
- Options with value type of stringArray mean that you can add multiple values. You can either separate values with a comma or add the flag twice.
<job-name> the name of the job.
When starting a container, always pull the image from the registry, even if the image is cached on the running node. This is useful when you are re-saving updates to the image using the same tag.
Arguments to pass to the command run on container start. Use together with
--command sleep --args 10000
The number of times the job will be retried before failing. The default is 6. This flag will only work with training workloads (when the
--interactiveflag is not specified)
Command to run at container start. Use together with
The number of successful pods required for this job to be completed. Used for Hyperparameter optimization. Use together with
CPU units to allocate for the job (0.5, 1, .etc). The Job will receive at least this amount of CPU. Note that the Job will not be scheduled unless the system can guarantee this amount of CPUs to the job.
Limitations on the number of CPU consumed by the job (0.5, 1, .etc). The system guarantees that this Job will not be able to consume more than this amount of GPUs.
Mark the job as elastic. For further information on Elasticity see Elasticity Dynamically Stretch Compress Jobs According to GPU Availability
-e stringArray | --environment stringArray
Define environment variables to be set in the container. To set multiple values add the flag multiple times (
-e BATCH_SIZE=50 -e LEARNING_RATE=0.2) or separate by a comma (
--gpu int | -g int
Number of GPUs to allocation to the Job. The default is no GPUs.
Use the host's ipc namespace. Controls whether the pod containers can share the host IPC namespace. IPC (POSIX/SysV IPC) namespace provides separation of named shared memory segments, semaphores and message queues. Shared memory segments are used to accelerate inter-process communication at memory speed, rather than through pipes or through the network stack
For further information see docker documentation
Use the host's network stack inside the container For further information see docker documentation
--image string | -i string
Image to use when creating the container for this Job
Mark this Job as Interactive. Interactive jobs are not terminated automatically by the system
(Deprecated) Shortcut for running a Jupyter notebook container. Uses a pre-created image and a default notebook configuration. Use the s flag instead.
Mount a large /dev/shm device. shm is a shared file system mounted on RAM
Use a local image for this job. A local image is an image which exists on all local servers of the Kubernetes Cluster.
CPU memory to allocate for this job (1G, 20M, .etc).The Job will receive at least this amount of memory. Note that the Job will not be scheduled unless the system can guarantee this amount of memory to the job.
CPU memory to allocate for this job (1G, 20M, .etc).The system guarantees that this Job will not be able to consume more than this amount of memory. The Job will receive an error when trying to allocate more memory than this limit.
Allows defining specific nodes (machines) or a group of nodes on which the workload will run. To use this feature your administrator will need to label nodes as explained here: Limit a Workload to a Specific Node Group This flag can be used in conjunction with Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set in the project. For more information see: Working with Projects
The number of pods this job tries to run in parallel at any time. Used for Hyperparameter optimization. Use together with
Expose ports from the Job container. Used together with
--port 8080:80 --service-type loadbalancer
--port 8080 --service-type ingress
Mark an interactive job as preemptible. Preemptible jobs can be scheduled above guaranteed quota but may be reclaimed at any time.
Prevent the job’s container and all launched processes from gaining additional privileges after the job starts. Default is
false. For more information see Privilege Escalation.
Mount a persistent volume claim into a container
The 2 syntax types of this command are mutually exclusive. You can either use the first or second form, but not a mixture of both.
Storage_Class_Name is a storage class name which can be obtained by running
kubectl get storageclasses.storage.k8s.io. This parameter may be omitted if there is a single storage class in the system, or you are using the default storage class.
Size is the volume size you want to allocate. See Kubernetes documentation for how to specify volume sizes
Container_Mount_Path. A path internal to the container where the storage will be mounted
Pvc_Name. The name of a pre-existing Persistent Volume Claim to mount into the container
--pvc :3Gi:/tmp/john:ro- Allocate
3GBfrom the default Storage class. Mount it to
--pvc my-storage:3Gi:/tmp/john:ro- Allocate
my-storagestorage class. Mount it to /tmp/john as read-only
--pvc :3Gi:/tmp/john- Allocate
3GBfrom the default storage class. Mount it to
--pvc my-pvc:/tmp/john- Use a Persistent Volume Claim named
my-pvc. Mount it to
--pvc my-pvc-2:/tmp/john:ro- Use a Persistent Volume Claim named
my-pvc-2. Mount it to
Run in the context of the current user running the Run:AI command rather than the root user. While the default container user is root (same as in Docker), this command allows you to submit a job running under your Linux user. This would manifest itself in access to operating system resources, in the owner of new folders created under shared directories etc.
--service-type string | -s string
Service exposure method for interactive Job. Options are:
nodeport, ingress. Use the command runai list to obtain the endpoint to use the service when the job is running. Different service methods have different endpoint structure
Templates are currently not supported
Define the duration, post job finish, after which the job is automatically deleted (5s, 2m, 3h, etc).
Note: This setting must first be enabled at the cluster level. See Automatically Delete Jobs After Job Finish
--volume stringArray | -v stringArray
Volume to mount into the container. Example
-v /raid/public/john/data:/root/data:roThe flag may optionally be suffixed with
:rwto mount the volumes in read-only or read-write mode, respectively.
Starts the container with the specified directory
Set the logging level. One of: debug|info|warn|error (default "info")
--project | -p (string)
Specify the project to which the command applies. Run:AI Projects are used by the scheduler to calculate resource eligibility. By default, commands apply to the default project. To change the default project use
runai project set <project-name>.
--help | -h
Show help text
start an unattended training job of name run1, based on project team-a using a quickstart image:
runai submit run1 -i gcr.io/run-ai-demo/quickstart -g 1 -p team-a
start an interactive job of name run2, based on project team-a using a Jupyter notebook image. The Notebook will be externalized via a load balancer on port 8888:
runai submit run2 -i jupyter/base-notebook -g 1 \ -p team-a --interactive --service-type=loadbalancer --port 8888:8888
The command will attempt to submit a job. You can follow up on the job by running
runai list or
runai get job-name -e
Note that the submit call may use templates to provide defaults to any of the above flags.
- See any of the Walk-through documents here: Run:AI Walk-through