> For the complete documentation index, see [llms.txt](https://docs.dunedocker.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dunedocker.app/getting-started/installation.md).

# Installation

Install a self-hosted Dune Awakening server with Dune Docker, complete the browser setup, and start your first Battlegroup.

Run the installer as a normal Linux user with sudo access. It downloads the latest public release, prepares the Console, and prints the browser address. Install curl and tar with your distribution's package manager first if they are missing.

```bash
curl -fsSL https://raw.githubusercontent.com/Red-Blink/dune-awakening-selfhost-docker/main/bootstrap.sh | sh
```

Do not run the installer as root or prefix it with sudo. The [GitHub README](https://github.com/Red-Blink/dune-awakening-selfhost-docker#installation) also provides download-tool alternatives.

## What Happens Next

1. Open the Console URL printed by the installer, normally on port `8088`.
2. Sign in with the generated administrator password.
3. Complete the guided setup with your Funcom token and server choices.
4. Start the Battlegroup and wait for readiness checks to pass.
5. Configure [firewall and router rules](/getting-started/networking.md) before inviting internet players.

The default project folder is `~/dune-awakening-selfhost-docker`. To choose a mounted drive, follow [Install on Another Drive](/how-do-i.../install-on-another-drive.md). The fresh installer requires a new destination; do not use it over an existing installation. Use the Console's Updates page instead.

On Windows, choose either [VMware with Ubuntu](/getting-started/install-dune-docker-on-windows.md) or [Ubuntu WSL2 with Docker Desktop](/how-do-i.../windows-wsl2.md). Do not run this Linux installer inside Docker Desktop's internal distribution.


---

# 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.dunedocker.app/getting-started/installation.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.