> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/guides/installing-lucy/upgrading-to-lucy-6.0/docker-deployments.md).

# Docker Deployments

### Before you start

Make sure you have:

* A Docker-based deployment
* Lucy version 5.7.6
* At least 60% free storage space on the host
* A recent snapshot or backup of the host machine

***

### 1. Stop all campaigns

Stop all active and scheduled campaigns before starting the migration.

The Lucy dashboard will be unavailable for the entire migration process. We recommend performing the upgrade during a maintenance window or during off-peak hours.

### 2. Free up storage space

The migration requires at least **60% free storage space on the host** to allow the existing Lucy container to be backed up and migrated.

If additional space is required, consider removing:

* Unedited templates that are no longer needed
* Unneeded campaigns
* Old exports
* Cached data

### 3. Create a host snapshot

The migration script creates a backup of the existing Lucy container. As an additional safety measure, we strongly recommend creating a snapshot of the **entire host machine** before starting the migration.

If the host is running on a virtualization platform, create the snapshot using the platform's normal snapshot functionality.

### 4. Download the migration script

Run the following command **on the host machine, not inside the Lucy container**:

```bash
wget https://download.phishing-server.com/dl/upgrade_container6.sh
```

### 5. Run the migration script

Run the following command **on the host machine, not inside the Lucy container**:

```bash
sudo bash upgrade_container6.sh
```

The migration may take several hours depending on the amount of data stored in Lucy.

When prompted, select:

* **Autodetect Lucy container** → `YES`
* **System snapshot** → `YES`

Allow the script to complete before proceeding.

### 6. Update Lucy in the UI

Once the migration script has finished, access the Lucy UI and complete the update to **Lucy 6.0**.

### 7. Verify the migration

After upgrading to Lucy 6.0, verify that the migration was successful and that the expected data is available and functioning correctly.

Check that the expected campaigns, templates, users, settings, and other required data are present.

### 8. Remove the old container

Only after you have confirmed that the migration was successful and everything is working correctly, remove the old container:

```bash
sudo docker rm lucy_old_backup
```

{% hint style="danger" %}
Do not remove `lucy_old_backup` until you have verified the migration. Once the old container has been removed, it can no longer be used as a fallback.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.lucysecurity.com/guides/installing-lucy/upgrading-to-lucy-6.0/docker-deployments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.