Docker Inspect action allows you output low-level information on Docker objects to a Continua CI variable.
A friendly name for this action (will be displayed in the actions workflow area).
Determines if this action will be run within the relevant stage.
The directory from where the Docker command will be run. This is important for relative directories passed to the Docker Command.
The ID or name of the object (e.g. container, image, volume, network, node, service, or task) to inspect.
The type of object that we are inspecting:
If you leave this as 'Any', a container will be inspected in preference to an image with the same name.
Choose the query format to use to select a value from the command output.
The relevant input boxes below will be shown for entering the associated template or query as each option is selected.
See the Docker command and log output documentation for examples . Command line option: --format
Tick to open a new Host tab to specify an alternative Docker host to the one local to the agent.
The version of Docker to use when running the Docker Inspect command. It is important that the agent have the correct version of Docker installed for the Docker File provided.
The address of the Docker Host. This can be in the form of a URL or any IP4 Address. If a non-standard port is required simply use the <IPAddress>:<Port> specitifcation format.
Tick to connect to the Docker host using TLS where the host is not verified against a CA.
This is available only if 'Use TLS' is ticked. Tick to verify the TLS certificate with a root authority.
When using Verify TLS, if the host's certification authority (CA) is not trusted by the agent, then the connection is not established.
Path to Docker host CA certificate file.
Path to Docker host certificate file
The Docker Host Certificate Key is the PEM format key file for the accessing the Docker Host Certificate.
Select the name of the build variable to set with the result of the inspection.
Tick to ignore any errors setting variable value. Log warning only.
Tick to include the total size of the files if the type is a container.
The amount of information detail to display in the build log.
How long to wait for the action to finish running before timing out. Leaving this blank (or zero) will default to 86400 seconds (24 hours).
Tick to continue build on failure marking the action with a warning status.
If this is ticked, any warnings logged will not mark the action with a warning status.
Multiple environment variables can be defined - one per line.
If this is ticked, environment variable values are written to the build log.
Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and variables.