Bug 1082344

Summary: LXC 1.0.2 is out
Product: [Fedora] Fedora Reporter: Daniele Viganò <dennyvatwork>
Component: lxcAssignee: Thomas Moschny <thomas.moschny>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cfeller, i, karlthered, lightdot, mhw, sagarun, thomas.moschny, twhitehead
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lxc-1.0.3-2.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-21 01:58:45 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 Daniele Viganò 2014-03-30 13:22:55 UTC 
Description of problem:

LXC 1.0.2 has been released on Feb. 27th. Fedora 21 and EPEL 7 are still providint a pre-1.0 (0.9.0) version of LXC.

Big improvements are availble since version 1.0.0 and API are now "stable".

Please push LXC 1.0.2 to Fedora 21 and EPEL 7. SPEC files can be provided if needed.

Thanks
Comment 1 Tyson Whitehead 2014-05-13 18:56:28 UTC 
Another big improvement (from the news release) is that it sounds like it properly handles systemd having mounted the root as shared.

https://linuxcontainers.org/news/ (search for rshared on the page)

Without this, lxc launches the container in the host environment (i.e., it doesn't successfully change the root to the containers root).

It would, therefore, be really great it we could also get this into Fedora 20 (or at least back port the rshared fix).  Here's the associated patch

https://github.com/lxc/lxc/commit/cc28d0b0a66bd956645dc7b8fc85b917711f2472

Thanks!  -Tyson
Comment 2 Michael H. Warfield 2014-06-04 18:56:32 UTC 
Actually, it's not the case that root is shared with 0.9.0 but, rather, that systemd is mounting devtmpfs in the container when it's started causing the host and the container to share the entire device space, resulting in the behavior observed.  This was fixed in 1.0.0 with further enhancements.  We're not at 1.0.3 and about to release 1.0.4.
Comment 3 Thomas Moschny 2014-06-05 18:52:16 UTC 
*** Bug 1102380 has been marked as a duplicate of this bug. ***