> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/docker-management-console.md).

# Docker management console

Configure Docker management console session settings in Remote Desktop Manager, including host, port, credentials, Docker socket path, and SSH key.

This article details the many settings and options available for ***Docker management console*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the entry opens. <em><strong>Default (inherited)</strong></em> uses the display mode resolved from the parent folder or the entry type.</td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. When the host comes from a linked or inherited host, the <em><strong>Host</strong></em> field of the <em><strong>General</strong></em> tab is disabled.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields of the <em><strong>General</strong></em> tab are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The host name or IP address of the Docker host. Required when the host is configured in the entry.</td></tr><tr><td><strong>Port</strong></td><td>The port used to connect to the Docker host. Click the value to choose another port. <em><strong>Default</strong></em> uses port 22.</td></tr><tr><td><strong>Username</strong></td><td>The username used to connect to the Docker host. Required when the credentials are configured in the entry.</td></tr><tr><td><strong>Password</strong></td><td>The password used to connect to the Docker host. Required when the credentials are configured in the entry and the <em><strong>SSH key</strong></em> tab is set to <em><strong>No private key</strong></em>.</td></tr><tr><td><strong>Path</strong></td><td>The path of the Docker socket on the remote host. When left empty, <code>unix:///var/run/docker.sock</code> is used.</td></tr></tbody></table>

### SSH key

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Private key</strong></td><td><p>The source of the private key used to authenticate:</p><ul><li><strong>No private key</strong></li><li><strong>File (local)</strong></li><li><strong>Embedded data</strong></li><li><strong>Linked</strong></li><li><strong>My personal SSH key</strong></li><li><strong>Privileged account</strong></li></ul><p>With <em><strong>My personal SSH key</strong></em>, click the edit button to modify your personal private key. <em><strong>My personal SSH key</strong></em> is hidden when a policy disables the personal private key. <em><strong>Privileged account</strong></em> is offered only when the data source supports privileged SSH keys and a PAM license is present. When the server supports merged PAM vaults, privileged accounts are selected under <em><strong>Linked</strong></em> instead.</p></td></tr><tr><td><strong>Vault</strong></td><td>The vault that contains the private key entry. Available with <em><strong>Linked</strong></em>.</td></tr><tr><td><strong>Entry</strong></td><td>The entry that holds the private key. Available with <em><strong>Linked</strong></em>, where the add button creates a private key entry and the clear button removes the selection. With <em><strong>Privileged account</strong></em>, click the browse button to select the account. Required.</td></tr><tr><td><strong>Search string</strong></td><td>The name of the private key entry to search for in the user vault. Available with <em><strong>Linked</strong></em> when the user vault is selected in <em><strong>Vault</strong></em> from a shared vault. Required.</td></tr><tr><td><strong>File</strong></td><td>The private key file on the local computer. Available with <em><strong>File (local)</strong></em>. Required, and the file must exist.</td></tr><tr><td><strong>Passphrase</strong></td><td>The passphrase of the private key. Available with <em><strong>File (local)</strong></em> and <em><strong>Embedded data</strong></em>.</td></tr><tr><td><strong>Always prompt for passphrase</strong></td><td>Ask for the passphrase each time the entry opens instead of saving it. Disables the <em><strong>Passphrase</strong></em> field. Available with <em><strong>File (local)</strong></em> and <em><strong>Embedded data</strong></em>.</td></tr><tr><td><strong>Private key data</strong></td><td>The private key stored in the entry. Use the buttons above the field to view, paste, browse for, or clear the key. Available with <em><strong>Embedded data</strong></em>. Required.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/docker-management-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
