> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/update.md).

# Update

To update your Docker instance and upgrade to a newer release version, please follow the following steps:

{% hint style="warning" %}
**Prioritize Instance Backup Before Updating:** Before proceeding with the update, it's highly advisable to back up your project. If a complete backup isn't feasible, you should consider the following:

* Generating a snapshot of your database.
* Safeguarding the environment variables stored in .env file by copying them to a secure location external to Jet Admin.
  {% endhint %}

{% hint style="info" %}
**Evaluate Your Applications** \
Before rolling out the new instance, it's crucial to thoroughly test it on your most important applications, especially those that use various resources and components. Consider creating test cases, a checklist, or an internal upgrade guide to streamline this process. This document can include specific details, such as contextual information and commands, serving as a valuable resource for your team. Once the tests are successful, proceed to upgrade your production instances.
{% endhint %}

### To upgrade your deployment to a more recent version of On-premise:

Navigate to the directory where the on-premise package was previously installed.

```
cd jet-onpremise
```

Update git repository&#x20;

```
git pull
```

Download  the latest  version of docker containers

```
docker-compose pull
```

{% embed url="<https://www.loom.com/share/fdd927392f954805a9a0ce82d2c5ef23?sid=18a6b013-96e3-427d-85ff-61824db4aebf>" %}

Restart the Jet Admin application (this process may take up to 30 seconds to minutes depending on your server). This action will restart all Jet Admin components and run them in the background.

```
docker-compose up -d
```

{% embed url="<https://www.loom.com/share/9c1dc9bc867e4e83b64f149cafd708ee?sid=e4e18af9-78ad-442f-b79e-341e69818e79>" %}

{% hint style="success" %}
**Performance Optimization (Optional)**

To improve runtime efficiency after your initial deployment, we recommend stopping additional JetAdmin migration containers once they have completed their tasks (typically within \~10 minutes post-deployment). On your on-premise server, run the following command to force-remove any residual migration containers:

`sudo docker ps -aq --filter "name=migrations_run" | xargs -r sudo docker rm -f`

This step helps free system resources and can enhance overall performance of your JetAdmin instance.
{% endhint %}


---

# 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.jetadmin.io/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/update.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.
