> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/1-10-1/documentation/installation-and-upgrades/uninstalling-connectware/uninstalling-connectware-docker.md).

# Uninstalling Connectware (Docker)

Uninstalling Connectware removes Connectware from your system, including all containers, volumes, and service configurations.

{% hint style="warning" %}
Make sure to back up any important data before proceeding with the uninstallation, as this process will permanently remove all Connectware-related data from your system.
{% endhint %}

1. Switch to the root user and navigate to your installation directory:

{% code lineNumbers="true" %}

```yaml
sudo -i
cd <installation-directory>
```

{% endcode %}

2. Stop and remove all Docker containers, networks, and volumes associated with Connectware:

{% code lineNumbers="true" %}

```yaml
docker compose down -v
```

{% endcode %}

3. Navigate up one directory level and delete the installation directory:

{% code lineNumbers="true" %}

```yaml
cd ..
rm -R <installation-directory>
```

{% endcode %}

If you have installed Connectware via systemd, proceed with the next steps.

4. systemd installations only: Disable the Connectware service.

{% code lineNumbers="true" %}

```yaml
systemctl disable connectware
```

{% endcode %}

5. Remove the service file:

{% code lineNumbers="true" %}

```yaml
rm /etc/systemd/system/connectware.service
```

{% endcode %}


---

# 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.cybus.io/1-10-1/documentation/installation-and-upgrades/uninstalling-connectware/uninstalling-connectware-docker.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.