Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1069599

Summary: [RFE] LXC -- userspace tools for the Linux kernel containers
Product: Red Hat Enterprise Linux 7 Reporter: michal novacek <mnovacek>
Component: distributionAssignee: RHEL Program Management <pm-rhel>
Status: CLOSED WONTFIX QA Contact: Nobody <nobody>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: acathrow, berrange, bsarathy, jdenemar, lsmid, notting, vpavlin
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 19:16:30 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 michal novacek 2014-02-25 11:26:17 UTC
Please include lxc to RHEL7.

Managing lxc containers will be much more user likeable if these tools existed. In current RHEL7 we only do have "virsh -c lxc:/// console" which does not allow any automation.

lxc is being built for fedora 20 seems to already to be build for EPEL:
https://dl.fedoraproject.org/pub/epel/6/x86_64/lxc-0.9.0-2.el6.x86_64.rpm

Homepage: http://linuxcontainers.org

Comment 1 Jiri Denemark 2014-02-25 11:44:41 UTC
This is not a libvirt bug. If you want new package to be added into RHEL, I believe you need to file a bug against the "distribution" component (or perhaps another one but definitely not libvirt).

Comment 3 Václav Pavlín 2014-02-25 13:35:51 UTC
As far as I know, we don't want to support lxc in RHEL7 - Luděk, am I right?

Comment 4 Daniel Berrangé 2014-02-25 14:53:18 UTC
Correct, there is no intention to include the 'lxc' userspace tools in RHEL. Even Docker is not going to be using or including the 'lxc' tools in the long term, switching to operate directly against the kernel cgroup/namespace APIs instead as libvirt does.

The original bug description here is seriously lacking in useful information about what the root cause problem to be solved is. If there are specific things that the lxc tools do, which libvirt does not currently support, those are likely to be valid candidates for RFEs against libvirt.

Comment 5 Bill Nottingham 2014-02-25 18:50:04 UTC
NAKing the bug as filed - if there are specific issues with libvirt, please file RFEs against libvirt.

Comment 6 RHEL Program Management 2014-02-25 19:16:30 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.