Support listing volumes

[jelly]

Rought mockup with basic volume listing

Let's add a basic listing and then delete support.

As follow up:

• Show sizes, there is a /system/df endpoint but it needs investigation on why its slow with btrfs graphDriver and other performance concerns
• Prune unused volumes like images
• Create volume support in the container page
• Export volume (download), which begs the question about import support.

Related to: #2342

[tomasmatus]

I like this, thanks! Another idea I have is to show which containers use the volume. Maybe a popover for the text in the "Used by" column?

[jelly]

I like this, thanks! Another idea I have is to show which containers use the volume. Maybe a popover for the text in the "Used by" column?

Right we have this for images!

So maybe an expandable makes sense here.

[rare-magma]

@jelly this would be a great addition to cockpit-podman, is there anything left to do before merging this PR? I'd be willing to help with implementing the display of the size of the volumes later on.

[gp-lnuff]

Any update on this?

[Venefilyn]

@jelly wanna rebase?

Let's add a basic listing and then

• Delete support

• Showing the size of the volumes

• Prune volumes

• Create volume in container

I think we should support these in the same PR. I think the initial work looks good, I'm wondering if we should do anything with volumes without a name, e.g. those created with just podman volume create as-is. It creates a large hash as the name and mount, but can always tackle this after the fact. For now nothing seems off about it