> 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/dockerfile.md).

# Dockerfile

Configure Dockerfile document entries in Remote Desktop Manager, including document storage mode, file source, display mode, and read-only access.

This article details the many settings and options available for ***Dockerfile*** document entries in Remote Desktop Manager.

{% hint style="info" %}
On Windows and Linux, Remote Desktop Manager also offers a ***Dockerfile editor*** entry type. It uses the same settings and starts a new entry with ***Create empty document*** selected.
{% endhint %}

<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. Select a folder from the list, browse to one, or click the add button to create a new folder.</td></tr><tr><td><strong>Display</strong></td><td><p>How the document opens:</p><ul><li><strong>External</strong></li><li><strong>Embedded (tabbed)</strong></li><li><strong>Undocked</strong></li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list. When the document opens undocked, pickers for the monitor and the virtual desktop appear beside the list.</p></td></tr><tr><td><strong>Mode</strong></td><td><p>The buttons at the top of the settings set where the document is kept:</p><ul><li><strong>Stored in database</strong></li><li><strong>Link to file</strong></li><li><strong>URL</strong></li></ul><p><em><strong>Stored in database</strong></em> keeps the document in the data source with the entry and is selected by default for a new entry. It is offered only when the data source can store the document, and an existing entry offers it only if the entry already uses it. <em><strong>Link to file</strong></em> points the entry to a file path, and <em><strong>URL</strong></em> points it to a web address.</p></td></tr><tr><td><strong>Source</strong></td><td><p>Shown for a new entry when the mode is <em><strong>Stored in database</strong></em>. Choose how to provide the document:</p><ul><li><strong>Upload existing file</strong></li><li><strong>Create empty document</strong></li></ul><p>With <em><strong>Create empty document</strong></em>, the blank file is created when you save, then opened for editing.</p></td></tr><tr><td><strong>Document name</strong></td><td>Shown when the source is <em><strong>Create empty document</strong></em>. The name of the blank file. Leave it empty to use the entry name. The <code>.dockerfile</code> extension is added automatically.</td></tr><tr><td><strong>Filename</strong></td><td>The document file. With <em><strong>Stored in database</strong></em> and <em><strong>Upload existing file</strong></em>, browse to the file to upload when creating the entry. On an existing entry, <em><strong>Update document</strong></em> replaces the stored file and <em><strong>Save as</strong></em> exports it to a file. On Windows and Linux, <em><strong>Save and edit content</strong></em> saves the entry and opens the document (the button reads <em><strong>Save and open</strong></em> when <em><strong>Read-only</strong></em> is checked). On a new entry that already holds a document, <em><strong>Clear</strong></em> removes it. A stored document cannot exceed the maximum file size set for the data source. With <em><strong>Link to file</strong></em>, enter or browse to the path of the file the entry opens. The filename is required in both modes.</td></tr><tr><td><strong>URL</strong></td><td>Shown when the mode is <em><strong>URL</strong></em>. The web address of the document, which must be a valid web URL. Click <em><strong>Navigate URL</strong></em> to open the address in the web browser.</td></tr><tr><td><strong>Use default credentials</strong></td><td>Shown when the mode is <em><strong>URL</strong></em>. Use the default credentials when downloading the document from the URL.</td></tr><tr><td><strong>Read-only</strong></td><td>Open the document in read-only mode. Not available when the source is <em><strong>Create empty document</strong></em>.</td></tr><tr><td><strong>File size</strong></td><td>The size of the document. This value is read-only.</td></tr><tr><td><strong>Created by</strong></td><td>The user who created the entry. This value is read-only.</td></tr><tr><td><strong>Creation date</strong></td><td>The date the entry was created. This value is read-only.</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/dockerfile.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.
