cockpit-podman icon indicating copy to clipboard operation
cockpit-podman copied to clipboard

CPU share and RAM limit is not visible

Open S-B-V opened this issue 4 years ago • 9 comments

After creating an container, where I specified all this things, it is not visible any more. At least I am not able to remember what volumes and environment variables I entered during creation. When I have to recreate the container in case of updates/testing... I have to elaborate everything from scratch if I did not created it via CLI where I can check the bash_history or saved the command somewhere... For me it is mandatory that I see everything what I am able to configure (at least if configured), otherwise there is no parity and it is inconsistent.

S-B-V avatar Apr 24 '20 09:04 S-B-V

i second the above request, i was looking to replace docker/portainer with podman/cockpit, but it feels the ui is currently still too limited. i would like to create and manage networks and volumes, and also view the settings which were used to create a container, and be able to update those parameters.

hurenkam avatar Jan 08 '21 16:01 hurenkam

Yikes.

This is definitely an oversight and we should show this at least in the details.

Hopefully we can add this ASAP. Sorry it hasn't been already. It should be shown.

garrett avatar Nov 18 '21 16:11 garrett

With environment variables being more dynamic than volumes it can feel limiting to manage them in the cockpit terminal.

BarryHuffman avatar Jan 06 '22 11:01 BarryHuffman

The memory limit is already shown, first one is limited to 100 MB the other one uses the default limit (our test vm so 1GB)

image

jelly avatar Jan 06 '22 14:01 jelly

Mounts (volumes) information is available in podman's rest api along with the readable/writeable status. SELinux labels do not seem to be exposed as of yet. Issue here https://github.com/containers/podman/issues/13038

image

jelly avatar Jan 27 '22 12:01 jelly

Did a bit of hacking myself, and came up with the following diff, which if applied against today's repository gives me volumes (mounts), networks, and environment variables in the detailed view. Now ideally there would be a way to edit these and recreate an existing container with the updated values. That's an exercise for another day ;-) diff.txt

hurenkam avatar Feb 17 '22 01:02 hurenkam

@hurenkam would you be interested in sending PR with your changes?

marusak avatar Feb 17 '22 06:02 marusak

I have added a pull request with my changes

hurenkam avatar Feb 17 '22 10:02 hurenkam

Link to PR

jelly avatar Feb 21 '22 10:02 jelly