> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeper-connection-manager/installation/docker-compose-install/upgrading.md).

# Upgrading

Upgrading Keeper Connection Manager with the Docker Manual Install method

{% hint style="warning" %}
Before making any changes to your environment, we recommend backing up in accordance with the [instructions on the Backup and Recovery page](/keeper-connection-manager/installation/backup-and-recovery.md).
{% endhint %}

To update all of the Keeper Connection Manager docker images when using the Docker Compose Install method, run the below command (assuming `docker-compose.yml` is in the current folder):

```
sudo docker-compose pull
sudo docker-compose up -d
```

If you originally installed with the Auto Docker Install method (kcm-setup.run script), run the below command:

```
sudo ./kcm-setup.run stop
sudo ./kcm-setup.run upgrade
```

Select "Y" when prompted.

If you run into any issues with the upgrade, see our [troubleshooting](/keeper-connection-manager/troubleshooting.md) page.


---

# 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.keeper.io/keeper-connection-manager/installation/docker-compose-install/upgrading.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.
