Portainer Agent broken - no access to the stack file

[BoBBer446]

Ask a Question!

Hello, something has happened to me that I can't understand at the moment.
I wanted to update some applications today and noticed that the agent is no longer there on my main server in the Portainer installation.
This means that I can no longer access my stack file

When I reinstall Portainer on the server, it always says:
This stack was created outside of Portainer. Control over this stack is restricted.

How do I get back to the stack file or find it?

[Nick-Portainer]

Hey @BoBBer446, so the agent connected to your main Portainer server was lost, and you re-deployed it to re-establish the connection. Now, all stacks on that agent environment are showing that message—correct? This should not have happened unless your Portainer Server was redeployed and the volume was also recreated

[BoBBer446]

Maybe something is corrupt. I can't find any compose file on /data :/

If I use docker inspect there is shown a compose file on /data/compose/8/... but the file is not existing anymore:/

[Nick-Portainer]

Was Portainer Server ever redeployed?

[BoBBer446]

Yes I was trying two times but I get the feeling the volume is gone :/
But I didn't know what happened if my server is rebooting:+
I need a way to get my compose file back

[BoBBer446]

Is there a solution?
I don't know how it could happen but after a restart of the server the containers start. According to docker inspect a yml file is used which does not exist on the server.
Portainer itself only shows this after a reinstallation of Portainer:
“This stack was created outside of Portainer. Control over this stack is limited.”

[BoBBer446]

i was able to fix it by using this:
https://github.com/Red5d/docker-autocompose

[Nick-Portainer]

Hey, I am curious how this fixed your issue? Was your volume deleted or were you not using it when you re-deployed and the auto compose managed to use the correct volume on deployment?