Some ideas

[lsv]

• List of what keys are able, just like in htop - fast overview :)
• How to force delete a image? 409 Client Error: Conflict ("b'conflict: unable to delete 3810ba4a12d7 (must be forced)
• When in a "tab" (like inspected a image, and I want to get back to overview, I would normally use q, but this closes sen completely, maybe use q to just close the "tab" (you call a tab a buffer, properly a vim thing?)
• @ refresh listing - so how does you type a @ - AltGr + 2 does not work?

[TomasTomecek]

List of what keys are able, just like in htop - fast overview :)

This is a very good idea! Especially when number of keys will likely grow in future. (personally I like this very much in mc/htop)

How to force delete a image?

Another solid RFE.

When in a "tab" (like inspected a image, and I want to get back to overview, I would normally use q, but this closes sen completely, maybe use q to just close the "tab" (you call a tab a buffer, properly a vim thing?)

You can use ctrl+o or ctrl+i (just like jumps in vim) to move to another buffer. There's also an issue opened #21 which suggests the same thing: q should just quit buffer, not the whole app. Since this is another request, I'm seriously considering of making it happen.

@ refresh listing - so how does you type a @ - AltGr + 2 does not work?

I'm using US keyboard layout and I type @ with shift+2.

Thanks a lot for your great suggestions!

[lsv]

I'm using US keyboard layout and I type @ with shift+2.

I had that in mind, so yeah, in scandinavian (im not sure if other countries) uses AltGr+2 for @, so maybe change this to a more "default" key.

I can see you haven't used many F keys, maybe utalize those more? - Most of htop keys are F keys, yes I know on Mac's that it requires two keys to get a Fx key.

Thanks a lot for your great suggestions!

You are welcome, and thanks for sharing this awesome project on reddit, and yes I have already used it, and found tons of images that are very old (many from the beginning of dockers life, so nice to get cleaned them out - and yes, as storage is not an issue, I haven't actually found time to inspect and clean them up - but with your tool, its so much easier.

Another suggestion - Im not sure if this is actually possible, but would it be a good suggestion to add the path from where the docker container got created from, and maybe mark it with red, if that path does not exists anymore?

[TomasTomecek]

Yup, using more f-keys sounds good.

To be honest, that was the reason I started sen -- to interactively remove my stall containers and images :)

to add the path from where the docker container got created from

I'm sorry but I don't understand, could you elaborate please? sen operates on responses from docker engine, so if that's available in inspect, it's doable.

[lsv]

I'm sorry but I don't understand, could you elaborate please? sen operates on responses from docker engine, so if that's available in inspect, it's doable.

On some containers, it is there, but its under mount points - Dont know what I was looking at, properly I was a bit to sleepy, I just saw my path on my machine :)

[TomasTomecek]

You can bind mount a directory from your host system inside containers:

-v /home/me/my/volume:/volume-data

As I understand your comment, you would like sen to check whether path /home/me/my/volume is still available on your host system.

I think this feature request makes sense: sen could stat that directory an report its findings. The only issue is that sen might not have permissions to access the directory.