Old Stacks are limited after switching from the Agent to Standalone

[domi-btnr]

Ask a Question!

Hello,

I recently made a change to my Server setup. I moved from the Portainer Agent to the standalone version since the 'master' Server no longer exists. I uninstalled the Agent using the documentation and then installed the standalone version using the same documentation. When I opened Portainer, I had to go through the setup process again. After that, I could access the local environment. All my containers were still there, and it even detected the Stacks. However, I can’t edit them anymore. I get an error message saying:

This stack was created outside of Portainer. Control over this stack is limited.

Can I give the new standalone install the permissions it needs to edit the Stacks again? I’m using the same volume for the standalone install as I did with the Agent version. I didn’t delete the disk, and all the old data should still be in the volume.

[Nick-Portainer]

Hi @domi-btnr,

Currently, we do not support migrating a Portainer agent environment to a standalone environment, which is why you are seeing limitations with your stacks. Even though you are using the same Portainer volume, the IDs in the Portainer database for your agent environment do not match those of your new standalone environment. As a result, Portainer treats this as a new local environment, with no knowledge of it being previously an agent environment. This is why the stacks you originally deployed via Portainer appear as limited.

There is currently no official method to bring these stacks under full control when switching an environment from an agent to standalone.

[domi-btnr]

I see. Thank you for your reply