You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am following this project for a few months and I was waiting for some maturity before diving into it, and I think its now time.
Because Arcane does have the features I miss the most in Portainer CE, and it seems to work flawlessly.
Now I am scratching my head on how to migrate smoothly.
Got >80 containers spread over 5 servers, all managed with portainer stacks.
The trash way to migrate would be to take everything down and recreate everything from my portainer Stacks' composes to arcane Projects.
But Before doing that I want to make sure that there's not a more elegant way to do it, ie dont shutdown my containers (and thus web-facing services) first.
Hello 👋🏻
I migrated from Portainer BE to Arcane a few months ago.
And you don’t really have much choice...
You will also need to have volumes mounted, otherwise you will lose the data when the container is recreated, because you will have no choice but to delete the existing containers (therefore the Portainer stacks) and recreate them from scratch in Arcane.
To do this, you need to shut down your containers properly. Make a backup. Delete the containers.
If you have correctly installed Arcane (and/or its agent) with the right folders on the disks, you can copy the data from the Portainer folder into Arcane’s projects folder.
Then you can recreate the stacks in Arcane (called projects) and redeploy the containers.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I am following this project for a few months and I was waiting for some maturity before diving into it, and I think its now time.
Because Arcane does have the features I miss the most in Portainer CE, and it seems to work flawlessly.
Now I am scratching my head on how to migrate smoothly.
Got >80 containers spread over 5 servers, all managed with portainer stacks.

The trash way to migrate would be to take everything down and recreate everything from my portainer Stacks' composes to arcane Projects.
But Before doing that I want to make sure that there's not a more elegant way to do it, ie dont shutdown my containers (and thus web-facing services) first.
Cheers
Beta Was this translation helpful? Give feedback.
All reactions