Re: [lxc-users] Systemd inside lxc
Greetings, Fajar A. Nugraha! systemd support is somewhat a fast-moving target. In the past it was possible to have old version of systemd running with old version of lxc, BUT the container can mess up the host due to unlimited privileges needed. Currently AFAIK you need lxcfs, lxc 1.1.x, latest systemd, and privileged container to have systemd running in the container. Wait, I need systemd ON HOST to run systemd container? If you don't have either one of them, you'll run into problems. Try installing the bits you're still missing. -- With best regards, Andrey Repin Wednesday, June 3, 2015 12:53:48 Sorry for my terrible english... ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] lxcfs 0.9
Hello, it seems on Github lxcfs 0.9 is out for quite a while now but there has been no source package uploaded to linuxcontainers.org. Is this on purpose? If not it would be great if you could put it up so I can update the corresponding arch package. Best, Christian pgpFjSX2dD8IB.pgp Description: PGP signature ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] kernel crash when starting an unprivileged container
On 2015-06-03 15:01, Tomasz Chmielewski wrote: I'm trying to start an unprivileged container on Ubuntu 14.04; unfortunately, the kernel crashes. # lxc-create -t download -n test-container (...) # lxc-start -n test-container -F Kernel crashes at this point. It does not crash if I start the container as privileged. - kernel used is 4.0.4-040004-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/ The issue was a bit weird: - I've updated the kernel to 4.1-rc6, no longer crashing - still, the container was not starting on 4.1-rc6 - it turned out that lxc-create -t download ... created the container with all files being 0-bytes for some reason (so, 0-byte /sbin/init and all other files being 0-byte) - exec file format (0-byte /sbin/init) was causing 4.0.4 kernel crash? Anyway, problem solved. -- Tomasz Chmielewski http://wpkg.org ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] LXCFS and ProcPS Interaction Issue
On Mon, Jun 1, 2015 at 9:11 PM, Serge Hallyn serge.hal...@ubuntu.com wrote: Quoting Robert Pendell (shi...@elite-systems.org): On Mon, Jun 1, 2015 at 8:42 PM, Serge Hallyn serge.hal...@ubuntu.com wrote: Quoting Robert Pendell (shi...@elite-systems.org): First some basic information so you know my environment... Host: Linode OS: Ubuntu 14.04.2 Kernel: Host supplied 4.0.1 -- also tested against PV-Grub loaded 4.1-RC4 Container Privilage: Unprivileged. shinji@icarus:/proc apt-cache policy lxcfs lxcfs: Installed: 0.7-0ubuntu2~ubuntu14.04.1~ppa1 Candidate: 0.7-0ubuntu2~ubuntu14.04.1~ppa1 Version table: *** 0.7-0ubuntu2~ubuntu14.04.1~ppa1 0 500 http://ppa.launchpad.net/ubuntu-lxc/daily/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I literally just noticed this today. When LXCFS is started and running ProcPS throws a Floating Point Exception. I do not know why this is the case. Oddly enough stopping LXCFS on the host and restarting the container makes the bug go away. Ideas? Anything I can test to isolate? Can you build 0.9.0 from the wily sources, just to make sure this isn't somethign fixed upstream? Also, if you can run lxcfs under gdb and get stack trace when it crashes that woudl be helpful. LXCFS Stopped shinji@trusty-x86:~ ps u USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND shinji1506 0.0 0.1 5816 3536 pts/4Ss+ 12:42 0:00 -bash shinji1519 0.0 0.1 5404 2684 pts/4S+ 12:42 0:00 tmux -2 -f /usr shinji1573 0.3 0.1 5696 3412 pts/5Ss 12:42 0:00 /bin/bash shinji1679 0.0 0.1 5228 2340 pts/5R+ 12:42 0:00 ps u LXCFS Started shinji@trusty-x86:~ ps u USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND Signal 8 (FPE) caught by ps (procps-ng version 3.3.9). shinji1521 0.0ps:display.c:66: please report this bug Floating point exception I could but I guess I forgot to mention on here that the issue was already identified when I ran a ticket on LXC. Ah, great, thanks. I went ahead and did that testing but I couldn't get lxcfs 0.9 to work at all. It built but it didn't seem to respond nor did LXC seem to attempt to use it. I removed lxcfs 0.7 before testing and had it install in the default location (/usr/local). At no time did it seem like the container was using lxcfs as all /proc contents were a mirror of the host. However I did check /var/lib/lxcfs/proc and found that, once again, meminfo was blank so it looks like that the issue does indeed persist regardless. The stacktrace was non-conclusive given that we already know the scenario that needs handled/patched. Robert Pendell shi...@elite-systems.org A perfect world is one of chaos. Keybase: http://keybase.io/shinji257 ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] LXC multi distribution installer boot2lxc VM based on Alpine Linux
On Thu, 4 Jun 2015 01:33:03 AM Tobby Banerjee wrote: https://www.flockport.com/start What's with this login first crap? https://www.flockport.com/download/flockport-install.tar.xz I don't appreciate being spammed on a public mailing list like this no matter how good you think your intentions are. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
