[Feat ure] Remove container feature

[hhoao]

Can you add the ability to remove containers feature?

[kiuma]

ok, it seems reasonable to me. .............................................................. *ANDREA CHIUMENTI* *Partner* Tel. +39 039 9639600 Mob. +39 348 8063547 Mail. ***@***.*** Via Gramsci, 10 - 20900 Monza P.Iva 09154830963 red.software.systems

…

On Thu, Aug 24, 2023 at 5:51 AM hhoao ***@***.***> wrote: Can you add the ability to remove containers feature? — Reply to this email directly, view it on GitHub <#39>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAESDCUVSRHRPPQHQUC4UVLXW3FTRANCNFSM6AAAAAA34MFGB4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[bittner]

Ciao ragazzi!

I love the reduced user interface of the extension! 😍 ... but, yes, the "Remove" container feature is missing.

Do you want a PR for this to be added?

[kiuma]

Ciao Peter, We could reintroduce it ... with many warings, when there was in the original version, I accidentally removed a container. On the other hand, there are still tasks that I prefer to do via console. I think that deleting from the extension would be perhaps too easy. There is also a very nice extension for VS code if you are interested. (So basically I could also add a delete op, but with an alert dialog kind of "Type DELETE if you really want to delete container X" is necessary) Andrea .............................................................. *ANDREA CHIUMENTI* *Partner* Tel. +39 039 9639600 Mob. +39 348 8063547 Mail. ***@***.*** Via Gramsci, 10 - 20900 Monza P.Iva 09154830963 red.software.systems

…

On Thu, Sep 28, 2023 at 2:58 PM Peter Bittner ***@***.***> wrote: Ciao ragazzi! I love the reduced user interface of the extension! 😍 ... but, yes, the "Remove" container feature is missing. Do you want a PR for this to be added? — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAESDCTZ25ZM2XIXRBNOS2DX4VYA3ANCNFSM6AAAAAA34MFGB4> . You are receiving this because you commented.Message ID: ***@***.*** com>

[bittner]

(So basically I could also add a delete op, but with an alert dialog kind of "Type DELETE if you really want to delete container X" is necessary)

Sure! A confirmation dialog would be totally fine. But keep it simple: A confirmation dialog with an OK/Cancel or Yes/No choice is sufficient.

After all, what's the problem when an image is deleted? You should be able to either rebuild it (when you're the developer) or download it again (when the image is provided by someone else).

Ideally, the operation should be possible only on stopped containers.