pub struct ContainerWithExecOpts<'a> {
pub expand: Option<bool>,
pub expect: Option<ReturnType>,
pub experimental_privileged_nesting: Option<bool>,
pub insecure_root_capabilities: Option<bool>,
pub no_init: Option<bool>,
pub redirect_stderr: Option<&'a str>,
pub redirect_stdout: Option<&'a str>,
pub stdin: Option<&'a str>,
pub use_entrypoint: Option<bool>,
}
Fields§
§expand: Option<bool>
Replace “${VAR}” or “$VAR” in the args according to the current environment variables defined in the container (e.g. “/$VAR/foo”).
expect: Option<ReturnType>
Exit codes this command is allowed to exit with without error
experimental_privileged_nesting: Option<bool>
Provides Dagger access to the executed command. Do not use this option unless you trust the command being executed; the command being executed WILL BE GRANTED FULL ACCESS TO YOUR HOST FILESYSTEM.
insecure_root_capabilities: Option<bool>
Execute the command with all root capabilities. This is similar to running a command with “sudo” or executing “docker run” with the “–privileged” flag. Containerization does not provide any security guarantees when using this option. It should only be used when absolutely necessary and only with trusted commands.
no_init: Option<bool>
If set, skip the automatic init process injected into containers by default. This should only be used if the user requires that their exec process be the pid 1 process in the container. Otherwise it may result in unexpected behavior.
redirect_stderr: Option<&'a str>
Redirect the command’s standard error to a file in the container (e.g., “/tmp/stderr”).
redirect_stdout: Option<&'a str>
Redirect the command’s standard output to a file in the container (e.g., “/tmp/stdout”).
stdin: Option<&'a str>
Content to write to the command’s standard input before closing (e.g., “Hello world”).
use_entrypoint: Option<bool>
If the container has an entrypoint, prepend it to the args.