[Bug 1191600] Re: User namespace is not enabled in 32-bit raring kernel
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 not enabled in 32-bit raring kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191600] Re: User namespace is not enabled in 32-bit raring kernel
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: http://lwn.net/Articles/541787/ Posted Mar 7, 2013 14:05 UTC (Thu) by BernardB (subscriber, #47903) [Link] Okay, having dug deeper, it turns out that the examples require CONFIG_USER_NS. As the article points out, 3.8 was still missing the changes for XFS and other filesystems. Unsurprisingly, Ubuntu 13.04 chose XFS and NFS support over CONFIG_USER_NS. Bummer :P http://permalink.gmane.org/gmane.linux.kernel.containers.lxc.general/4755 I am going to try the kernel from https://launchpad.net/~ubuntu- lxc/+archive/kernel (“Ubuntu LXC team” team PPA) and will post my results here. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191600] [NEW] User namespace is not enabled in 32-bit raring kernel
Public bug reported: lxc-checkconfig reports that user namespace is missing in raring 32 bit. uname -a: Linux example 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:30 UTC 2013 i686 athlon i686 GNU/Linux /proc/version_signature: Ubuntu 3.8.0-25.37-generic 3.8.13 lspci output: N/A (lspci not installed in this configuration) lxc-checkconfig: root@example:/# lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.8.0-25-generic --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: missing ^^^ Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup namespace: required Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig This may be caused by the kernel config used in this package: CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y that is, CONFIG_USER_NS was not selected in the kernel configuration. For comparison, similar section in the kernel config of 64-bit Precise (12.04) looks as follows: CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y User namespace is the only one missing in the 32-bit version vs. 64-bit version. As result, lxc-start of a container with lxc.id_map is not possible (clone() returns EINVAL). Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191600] Re: User namespace is not enabled in 32-bit raring 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 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+attachment/3705265/+files/trace_with_id_map -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191600] Re: User namespace is not enabled in 32-bit raring kernel
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 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+attachment/3705266/+files/trace_without_id_map ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191600] Re: User namespace is not enabled in 32-bit raring kernel
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 kernel configuration supplied rather than in some software malfunction. Attached: output of lspci -vnvn. ** Attachment added: output of lspci -vnvn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+attachment/3705264/+files/lspci -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281361] Re: LTSP root account still locked with --prompt-rootpass
Unfortunately the issue with locked-out terminal root account still exists in Hardy. -- LTSP root account still locked with --prompt-rootpass https://bugs.launchpad.net/bugs/281361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45722] Re: flashplugin-nonfree doesn't uses the proxy debconf key
Hi, Same thing, on Ubuntu 8.04, I just got hit by this issue. But for those who are not packaging purists, it is possible just to go to the Adobe website, and download/install the plugin. I did that just 15 minutes ago, works fine. And it is user-level installation, so the package database is not touched. Thanks. -- flashplugin-nonfree doesn't uses the proxy debconf key https://bugs.launchpad.net/bugs/45722 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 134037] Re: Package too old, please drop it
Thanks. Once I have the current version of HSFFIG in order, I'll suggest it for packaging. On 8/24/07, Martin Pitt [EMAIL PROTECTED] wrote: Will remove the following packages from gutsy: hsffig |0.1.2-2 | source, amd64, hppa, i386, ia64, powerpc, sparc --- Reason --- (pitti) does not work with current ghc, request of upstream author -- Going to remove the packages now. Thanks for your notice! ** Changed in: hsffig (Ubuntu) Status: Triaged = Fix Released -- Package too old, please drop it https://bugs.launchpad.net/bugs/134037 You received this bug notification because you are a direct subscriber of the bug. -- Dimitry Golubovsky Anywhere on the Web -- Package too old, please drop it https://bugs.launchpad.net/bugs/134037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134037] Package too old, please drop it
Public bug reported: Binary package hint: hsffig I am Dimitry Golubovsky, developer of HSFFIG. The version 0.1.2-2 you are packaging was written with GHC 6.2.2 and old versions of packages required. It will not compile with GHC-6.6.x. Besides, changes in C preprocessor behavior in gcc 4.x make preprocessor output contents unsuitable for HSFFIG. I am working on accomodating of these changes. In the meanwhile I am requesting that you do not include HSFFIG of old versions in any UBUNTU distributions. Nobody will be able to use it anyway. I asked Debian maintainers to do the same, there was no response. I hope that UBUNTU maintainers will demonstrate better understanding. Thank you. Feel free to contact me if you have any questions. Dimitry ** Affects: hsffig (Ubuntu) Importance: Undecided Status: New -- Package too old, please drop it https://bugs.launchpad.net/bugs/134037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
