container run, but leaves the container stopped after creation.
Usage
Arguments
Image name
Container init process arguments
Process options
Set environment variables (format: key=value)
Read in a file of environment variables (key=value format, ignores # comments and blank lines)
Set the group ID for the process
Keep the standard input open even if not attached
Open a TTY with the process
Set the user for the process (format: name|uid[:gid])
Set the user ID for the process
Set the initial working directory inside the container
Resource options
Number of CPUs to allocate to the container
Amount of memory (1MiByte granularity), with optional K, M, G, T, or P suffix
Management options
Set arch if image can target multiple architectures
Write the container ID to the path provided
Run the container and detach from the process
DNS nameserver IP address
Default DNS domain
DNS options
DNS search domains
Override the entrypoint of the image
Run an init process inside the container that forwards signals and reaps processes
Use a custom init image instead of the default. This allows customizing boot-time behavior before the OCI container starts, such as running VM-level daemons, configuring eBPF filters, or debugging the init process.
Set a custom kernel path
Add a key=value label to the container
Add a mount to the container (format:
type=<>,source=<>,target=<>,readonly)Use the specified name as the container ID
Attach the container to a network
Do not configure DNS in the container
Set OS if image can target multiple operating systems
Publish a port from container to host (format: [host-ip:]host-port:container-port[/protocol])
Platform for the image if it’s multi-platform. This takes precedence over —os and —arch
Publish a socket from container to host (format: host_path:container_path)
Mount the container’s root filesystem as read-only
Remove the container after it stops
Enable Rosetta in the container
Set the runtime handler for the container
Forward SSH agent socket to container
Add a tmpfs mount to the container at the given path
Bind mount a volume into the container
Expose virtualization capabilities to the container (requires host and guest support)
Registry options
Scheme to use when connecting to the container registry. One of (http, https, auto)