Bug 1732713

Summary:	Run container from cockpit-podman with memory limit doesn't work
Product:	Red Hat Enterprise Linux 8	Reporter:	Chao Ye <cye>
Component:	cockpit-podman	Assignee:	Matej Marušák <mmarusak>
Status:	CLOSED ERRATA	QA Contact:	Jan Ščotka <jscotka>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	ajia, jscotka, mmarusak, mpitt
Target Milestone:	rc
Target Release:	8.2
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:47:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chao Ye 2019-07-24 07:58:03 UTC

Description of problem:
Run any container with memory limit from cockpit-podman WebUI doesn't work.

Version-Release number of selected component (if applicable):
# rpm -qa | grep ^cockpit
cockpit-podman-3-1.module+el8.1.0+3406+d3857ea7.noarch
cockpit-system-196-1.el8.noarch
cockpit-packagekit-196-1.el8.noarch
cockpit-ws-196-1.el8.x86_64
cockpit-pcp-196-1.el8.x86_64
cockpit-196-1.el8.x86_64
cockpit-bridge-196-1.el8.x86_64


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Martin Pitt 2019-08-08 06:10:27 UTC

This was originally introduced in https://github.com/cockpit-project/cockpit-podman/commit/56b6478fdcb . At that time this setting did not actually work through podman: https://github.com/containers/libpod/issues/2277

But this got fixed, so we need to wire this up and add an integration test for it.

Comment 2 Matej Marušák 2019-08-13 10:22:39 UTC

Upstream fix https://github.com/cockpit-project/cockpit-podman/pull/178

Comment 8 errata-xmlrpc 2020-04-28 15:47:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1650