Namespace Container

A list of string arguments for the ENTRYPOINT process of the container.

Many containers use an ENTRYPOINT process pointing to a shell {@code /bin/bash}. For those containers, you can use the argument list to specify the main command in the container process.

The availability domain where the container instance that hosts the container runs.

This command overrides ENTRYPOINT process of the container. If you do not specify this command, the existing ENTRYPOINT process defined in the image is the default.

The OCID of the compartment that contains the container.

The OCID of the container instance that the container is running on.

The number of container restart attempts. Depending on the restart policy, a restart might be attempted after a health check failure or a container exit. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}.

A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.

A map of additional environment variables to set in the environment of the ENTRYPOINT process of the container. These variables are in addition to any variables already defined in the container's image.

The exit code of the container process when it stopped running. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The fault domain of the container instance that hosts the container runs.

Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}

List of container health checks

The OCID of the container.

The container image information. Currently only supports public Docker registry.

You can provide either the image name (containerImage), image name with version (containerImagev1), or complete Docker image URL {@code docker.io/library/containerImage:latest}.

If you do not provide a registry, the registry defaults to public Docker hub {@code docker.io/library}. The registry used for the container image must be reachable over the VNIC of the container instance.

Determines if the container will have access to the container instance resource principal.

This method utilizes resource principal version 2.2. For more information on how to use the exposed resource principal elements, see https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdk_authentication_methods.htm#sdk_authentication_methods_resource_principal.

A message that describes the current state of the container in more detail. Can be used to provide actionable information.

The current state of the container.

Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}.

The time the container was created, in the format defined by RFC 3339.

The time when the container last deleted (terminated), in the format defined by RFC 3339.

The time the container was updated, in the format defined by RFC 3339.

List of the volume mounts.

The working directory within the container's filesystem for the container process. If not specified, the default working directory from the image is used.