How to Safely Redeploy a Container on AccuWeb.Cloud Without Losing Data?

Redeploying your container might sound tricky, but it’s actually pretty simple.

Don’t worry — if you follow the right steps, your important data (volumes) will stay safe.

Whether you’re updating to a new version or fixing a bug, we will guide you step by step.

Let’s get started!

What Does “Redeploy a Container” Mean?

Imagine your container is a box running your app. When you redeploy, you’re replacing that box with a fresh, updated one, maybe with bug fixes or new features, without touching the stuff you want to keep (like uploaded files, databases, or logs).

What Happens Behind the Scenes?

When you redeploy on Accuweb.Cloud:

1. A new container is created using the updated template or version.

2. Your important data paths (volumes) are identified.

3. The old container is stopped, and its system files are replaced with files from the new version.

4. Your volume data is kept safe, as long as the “Keep volumes data” option is checked.

In short: your app gets updated, and your precious data stays exactly where it was.

Step-by-Step: Redeploy via the Dashboard (Without Losing Volume Data)

You’ll need access to your environment via the Accuweb.Cloud dashboard.

1. Open Your Environment

• Log in to the dashboard.
• Navigate to your environment (where your app is running).

2. Trigger Redeploy

You’ve got two options to start the redeploy:

• Click the “Redeploy Container(s)” button next to your container or layer.
• Or, click the pencil icon next to the container version in the Topology Wizard.

Both ways will open the “Redeploy Containers” dialog box.

3. Choose the New Tag (Version)

• In the dialog, select the new Tag (select the desired tag corresponding to the container image version you want to deploy).
• Example: 2.4.64-php-8.4.10-almalinux-9 → 2.4.64-php-8.3.23-almalinux-9.

4. Enable “Keep Volumes Data” (Important)

This step is critical to prevent any data loss during the redeployment process.

Make sure to check the box labeled “Keep volumes data” before proceeding.

This option ensures that important data, such as database contents or user-uploaded files, is preserved. These files are stored in data volumes that are mounted inside your container.

You can view these volumes under the Volumes tab. This tab lists the paths where data volumes are mounted within the container. These volumes are intended to retain data across container restarts or replacements, allowing the data to persist independently of the container’s lifecycle.

If this option is not selected, all data stored in these volumes will be erased during redeployment.

5. Click Redeploy

• Hit the Redeploy button.
• Confirm in the popup.

That’s it! The platform will handle the redeployment process automatically from this point onward.

What You’ll See When It’s Done

After the redeploy process finishes, a success notification will appear in the top-right corner of the dashboard. Your container will now be running the new version, with your data safe and sound.

Before redeploy:

The application is running with existing data stored in mounted volumes (e.g., uploaded files).

After redeploy (with “Keep volumes data” enabled):

Container has been updated to the new version. All previously stored data in volumes is still intact and accessible.

Final Tips

• Always double-check that “Keep volumes data” is enabled before confirming.
• Redeploy during off-hours or maintenance windows if your app is live.
• Consider taking a snapshot or backup before large changes, just in case!