After manually deleting some versions of the docker-compose stacks now portainer and move the last version in folder for version 1, im left with portainer not able to access the docker-compose.yml.
I manually back the .ymls and .stack_envs remove the stack from portianer and remake them but this is a mess for multiple stacks.
I was thinking that by deleting them portianer will also "forget" them but it doesnt actually parse the directory to check the versions that exist, it stores the information in some kind of DB and search for the paths he takes form there.
We need either a way to scan the main directory or edit the paths our selfs. in the same logic we can also delete old versions..
I dont find any reason to keep 20 versions of the same stack without having a way to remove them.
After manually deleting some versions of the docker-compose stacks now portainer and move the last version in folder for version 1, im left with portainer not able to access the docker-compose.yml.
I manually back the .ymls and .stack_envs remove the stack from portianer and remake them but this is a mess for multiple stacks.
I was thinking that by deleting them portianer will also "forget" them but it doesnt actually parse the directory to check the versions that exist, it stores the information in some kind of DB and search for the paths he takes form there.
We need either a way to scan the main directory or edit the paths our selfs. in the same logic we can also delete old versions..
I dont find any reason to keep 20 versions of the same stack without having a way to remove them.
Originally posted by @zzecool in https://github.com/portainer/portainer/issues/10036#issuecomment-2053644493