Skip to content

WithDefaultTerminalCommand doesn't support privileged or nesting #6712

@shykes

Description

@shykes

Problem

Container.WithDefaultTerminalCommand allows configuring the command to be executed by Container.Terminal. But some execution options are not available:

Option Description Available in withExec Available in withDefaultTerminalCmd
experimentalPrivilegedNesting Allow the executed command to make API calls to the Dagger Engine running it
insecureRootCapabilities Execute the command in a privileged linux container

Solution

Add the missing arguments to Container.withDefaultTerminalCmd.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions