Add force tag when deleting images in version chooser

[JoaoMario109]

Closes #2431

[Williangalvani]

will this actually alllow the api to delete the currently running image? would this kill the container?
can you try it at http://blueos.local:8081/v1.0/ui/#/default/main.delete_version ?

[JoaoMario109]

will this actually alllow the api to delete the currently running image? would this kill the container? can you try it at http://blueos.local:8081/v1.0/ui/#/default/main.delete_version ?

I added the force option because it enables the removal of the image even in cases where a container was stopped but not terminated. Within our existing model, the BlueOS frontend initiates a delete operation only for images that are not currently running. Therefore, introducing the force option will not alter the existing behavior. However, it will provide a safeguard by ensuring that images can still be removed under certain conditions. For instance, if a container is manually stopped on the Raspberry Pi but not terminated, and a subsequent attempt is made to delete the image, without the force option, the image would remain as a dangling image, preventing its deletion.

[Williangalvani]

will this actually alllow the api to delete the currently running image? would this kill the container? can you try it at http://blueos.local:8081/v1.0/ui/#/default/main.delete_version ?

I added the force option because it enables the removal of the image even in cases where a container was stopped but not terminated. Within our existing model, the BlueOS frontend initiates a delete operation only for images that are not currently running. Therefore, introducing the force option will not alter the existing behavior. However, it will provide a safeguard by ensuring that images can still be removed under certain conditions. For instance, if a container is manually stopped on the Raspberry Pi but not terminated, and a subsequent attempt is made to delete the image, without the force option, the image would remain as a dangling image, preventing its deletion.

I understand your point, my concern is that someone could use the API to delete the image from the currently running container, in that case I'm not sure what would happen.

BUT, after seeing the code, I see we already have a safeguard for that, so we're good =]