Removal of stack created from the CLI

[cdavid15]

Ask a Question!

👋🏻

I think this will have been asked before but couldn't find any concrete details within the issues to answer my query.

When working locally I have a local plugin which allows to be rebuild my whole app via a fairly complex deployment script which results in my stack being deployed, services fully configured and then the databases (mongo, elastic, neo4j) all properly seeded.

I was running 2.15 and this allowed me to then destroy my stack from UI. When i attempted to bump to 2.19 last year we rain into the "This stack was created outside of Portainer. Control over this stack is limited." message and reverted back to 2.15. When upgrading to 2.24 today I am still seeing the same restriction (had hoped it would have been restored)

Is there a reason or a way I can create my stack via docker stack deploy via the CLI and still manage to delete it via the portainer UI? I am sure there will be reasons behind this but struggling to find out anything to explain why this is the case and why it can't be removed even though it wasn't created via the front end?

Cheers

[Nick-Portainer]

Hi @cdavid15 If you wish to delete a limited stack you can go to into it via Portainer and delete the containers within the stack which will remove the stack itself. I've raised this question though around why this was removed at the top level in newer versions and I'll let you know once I hear from the team.

[cdavid15]

Thanks @Nick-Portainer for the suggestion! I never even considered removing services from within the stack but this works well and still allows me to remove the stack quite easily.

It would be handy to do it on the stack page itself but the workaround will be perfect just now and allow us to upgrade.

Thanks!