This is an issue with the 64 bit kernels too.
** Summary changed:
- User namespace is not enabled in 32-bit raring kernel
+ User namespace is not enabled in raring kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Earlier, someone reported a similar problem in Quantal:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191600
Title:
User namespace is
Is this not an issue with the 64 bit kernels?
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191600
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Actually, I see you already stated that in the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191600
Title:
User namespace is not enabled in 32-bit raring kernel
To manage
This latest v3.10 kernel referred to in the previous comment did not
work for me by the same reason: CONFIG_USER_NS was not defined in the
build.
It is possible that the following two links explain the reason behind
the decision not to enable CONFIG_USER_NS in the 13.04 kernel:
This is the strace output recorded when trying to start a container with
lxc.id_map in config, that is, requiring user namespace. See the second
clone() call which fails with EINVAL.
** Attachment added: strace of lxc-start of a container requiring user
namespace
This is the strace output recorded when starting a container without lxc.id_map
in config, that s, not requiring user namespace.
All calls to clone are successful.
** Attachment added: strace of lxc-start of a container not requiring user
namespace
I am unable to run apport on this installation: it is intended to be a
minimal memory-resident Ubuntu base with very limited set of packages,
so apport (and its python counterpart) is not to be installed there.
Besides, by the nature of the issue being reported, the source of the
issue is in the
