Disable CONFIG_NET_NS (for #720095) breaks LXC
Bug #796937 reported by
Trent W. Buck
This bug report is a duplicate of:
Bug #790863: Unable to start lxc container after update to 2.6.32-32.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
New
|
Critical
|
Unassigned | ||
| lxc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
affects ubuntu/lxc
affects ubuntu/linux
importance critical
tag regression-updates
done
Justification: LXC is the *ONLY* lightweight virtualization system
available in Lucid; without it, the next lightest is KVM.
My containers need their own network stacks. After upgrading from
2.6.32-31 to -32, my containers completely failed to start. I believe
this is because you removed CONFIG_NET_NS for #720095. This *may*
even break containers that share host node's network stack, I haven't
checked.
The lxc package includes an "lxc-checkconfig" script you can use to
check the compile-time options of the running kernel.
To post a comment you must log in.
