Add support for pods (and some Ui refactoring)

[KKoukiou]

• fix tests

[KKoukiou]

@marusak @garrett I did not show yet the open ports and created time of the pod since the current mock up does not incoorporate them and I did not want to innovate too much.
I think it's fine that the pods attributes will me implemented in a followup.

[marusak]

List of TODOs: (I'll convert them into issues when this PR lands)

• Create new pod
• Pod actions (Delete, start/stop, pause/unpause)
• Add container to pod
• Add podless container
• pod details (ID, name, status, created, owner, ports) (owner not needed for containers then)

[marusak]

This looks amazing, thank you!

I wrote down list of follow-ups, please feel free to edit this list. I'll convert it into issues once this lands.

My main problem is with sorting and filtering. It seems to be container-centric, which sometimes does not make much sense (especially with owner).

[garrett]

OK, so I've fixed the page's height (so it always stretches), fixed the stickiness of the filter bar, adjusted the spacing of the pods in all the scenarios I've encountered, and even included a Star Wars reference as a joke (that will be lost when this is squashed down 😉).

@KKoukiou: I hope I didn't break anything in 628e995, when I removed a nested wrapper.

[marusak]

Thank you @KKoukiou for the changes, now it works much better!
There seems to be some problem though:

$ podman pod ps
POD ID        NAME      STATUS   CREATED        # OF CONTAINERS  INFRA ID
88fb67086715  user_one  Running  3 minutes ago  3                ebcfad8f79be
a25674684d34  user_pod  Created  21 hours ago   1                9378c45561e0

So I have one rootless pod that is running and there are 2 running containers in it, but when I pick Show Only Running it disappears. Are you able to reproduce, or should I do it locally?

$ podman pod create --name=user_one
$ podman run -dit --pod user_one fedora bash
$ podman run -dit --pod user_one fedora bash
In UI switch to see only running.

EDIT: When I refresh the page it is fine. Is it possible that we don't recognize when pod state changes? (no event/no processed event)

[KKoukiou]

$ podman pod create --name=user_one
$ podman run -dit --pod user_one fedora bash

Added a HACK in our code and opened an issue to podman.

[marusak]

Thank you!