centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-14: R8S-917 - Add Kompose support for Docker to Kube migration

Browse Source
This commit is contained in:
Hannah Cooper
2026-03-16 03:13:36 +00:00
committed by gitbook-bot
parent b892ec70b2
commit 53e0d849ee
5 changed files with 29 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
.gitbook/assets/2.40-navigate-to-stack.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 MiB

BIN
.gitbook/assets/2.40.0-Migrate-a-stack.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 32 KiB

BIN
.gitbook/assets/2.40.0-Migrate-to-K8s.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 52 KiB

BIN
.gitbook/assets/2.40.0-Rename-a-stack.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 30 KiB

37
user/docker/stacks/migrate.md
View File

@@ -8,13 +8,34 @@ metaLinks:
To migrate, duplicate, or rename a stack, open your environment, go to **Stacks**, and select the stack you want to change.
<figure><img src="../../../.gitbook/assets/2.36.0-duplicate-migrate-stacks.gif" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.40-navigate-to-stack.gif" alt=""><figcaption></figcaption></figure>
## Migrating a stack
In the **Stack duplication / migration** section, select the destination environment for the stack, and optionally define a new name for the stack. Click **Migrate**.
### Docker Compose to Kubernetes migration
<figure><img src="../../../.gitbook/assets/2.36.0-stacks-migrate.png" alt=""><figcaption></figcaption></figure>
{% hint style="warning" %}
Migrating Docker stacks to Kubernetes is currently an experimental feature and is not recommended for production workloads.
Before starting the migration, we recommend [taking a backup](../../../admin/settings/general.md#back-up-portainer).
{% endhint %}
Portainer allows you to migrate your Docker Compose workloads to Kubernetes. This feature uses the [Kompose](https://kompose.io/) tool to convert Docker Compose definitions into Kubernetes resources.&#x20;
From the stack you want to migrate, select **Migrate this stack**. In the dialog box that appears, select your Kubernetes environment as the destination for the migration, then complete the fields as described below. Click **Migrate**.
| Field | Overview |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Namespace | Specify the [namespace](../../kubernetes/namespaces/) you wish to migrate to. If the namespace you enter does not exist, a new one will be created during migration. |
| Convert to Helm chart | Toggle this on to convert your stack to a Helm chart. Note that if migrating to a Helm chart, the preview function will no longer be an option. |
<figure><img src="../../../.gitbook/assets/2.40.0-Migrate-to-K8s.png" alt=""><figcaption></figcaption></figure>
### Migration between Docker environments
From the stack you want to migrate, select **Migrate this stack**. Select the destination environment for the stack, and optionally define a new name for the stack. Click **Migrate**.
<figure><img src="../../../.gitbook/assets/2.40.0-Migrate-a-stack.png" alt=""><figcaption></figcaption></figure>
Migrating does not relocate the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Migrate**.
@@ -22,16 +43,16 @@ Migrating does not relocate the content of any persistent volumes that may be at
## Duplicating a stack
In the **Stack duplication / migration** section, give the new stack a descriptive name then select the environment the stack should duplicate to. When you're ready, click **Duplicate**.
From the stack you want to duplicate, select **Migrate this stack**. Give the new stack a descriptive name then select the environment the stack should duplicate to. Click **Duplicate**.
<figure><img src="../../../.gitbook/assets/2.36.0-stacks-migrate.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.40.0-Migrate-a-stack.png" alt=""><figcaption></figcaption></figure>
## Rename a stack
In the **Stack duplication / migration** section, give the stack a new descriptive name and select the environment that the stack is currently on. When you're ready, click **Rename**.&#x20;
From the stack you want to rename, select **Migrate this stack**. Give the stack a new descriptive name and select the environment that the stack is currently on. Click **Rename**.&#x20;
<figure><img src="../../../.gitbook/assets/2.36.0-stacks-rename.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.40.0-Rename-a-stack.png" alt=""><figcaption></figcaption></figure>
Renaming creates a new stack instance and does not transfer the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Rename**.
Renaming the stack creates a new stack instance and does not transfer the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Rename**.
<figure><img src="../../../.gitbook/assets/2.38-Stack-rename.png" alt=""><figcaption></figcaption></figure>