On Sun, Feb 08, 2015 at 05:30:19PM +0100, Thouraya TH wrote:
Hello all :)
*Is there a tutorial that specifies the data that will be imported
during a migration of a container? only CRIU **images?*
*Tycho: Both the CRIU images and the container disk will be moved; you
can seethis
On 31-1-2015 19:21, Dirk Geschke wrote:
LXC
should work fine for unprivileged containers at least with Ubuntu vivid
and Debian unstable, other distros typically have an older systemd which
hangs during the boot sequence.
Now I have (...) Debian wheezy. it fails with systemd:
(...)
and the
Quoting Dirk Geschke (d...@lug-erding.de):
Hi all,
I just to follow
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
once more to install a new container and it fails. First of all it
was a problem with the access to the directory
~/.local/share/lxc/jessie1
I think I can help here. Systemd-based unprivileged containers will only work
properly with systemd compiled from git (master) or systemd 218 patched with:
From: Lennart Poettering lenn...@poettering.net
Date: Thu, 8 Jan 2015 23:12:16 +0100
Subject: core: make EPERM errors when applying OOM
For the ones unfamiliar with patching software, here is are links to my
Google Drive with patched systemd-versions for Fedora 21 and Rawhide,
and Archlinux:
Fedora:
(1) systemd
https://drive.google.com/file/d/0B_UAut69TSAiTmI3SnN4TzRTaXM/view?usp=sharing
(2) systemd-libs
Hi Serge,
now I started lxcfs within gdb:
(gdb) where
#0 0x7706b610 in __recvmsg_nocancel ()
at ../sysdeps/unix/syscall-template.S:82
#1 0x00403cdd in recv_creds (sock=8, cred=0x7fffe5b0,
v=0x7fffe5af 1\377\377\377\377\377\377\377\377\377\377\377\377\001)
Quoting Xavier Gendre (gendre.rei...@gmail.com):
Thanks for your answer. Indeed, it only needs to be done at login
and this is my problem. Your solutions work well but all need to
login at least one time for each user with unprivileged containers.
I admit that my question was not clear :-°
Just out of curiosity, how do I exit lxc-top in Ubuntu 14.04?
The letter q means quiet. I do a Ctrl-C, to exit, but I am sure there
must be a cleaner way. The man lxc-top says nothing about this
___
lxc-users mailing list
Quoting Dirk Geschke (d...@lug-erding.de):
Hi Serge,
now I started lxcfs within gdb:
(gdb) where
#0 0x7706b610 in __recvmsg_nocancel ()
at ../sysdeps/unix/syscall-template.S:82
#1 0x00403cdd in recv_creds (sock=8, cred=0x7fffe5b0,
v=0x7fffe5af
Quoting Dirk Geschke (d...@lug-erding.de):
Hi Serge,
now I started lxcfs within gdb:
(gdb) where
#0 0x7706b610 in __recvmsg_nocancel ()
at ../sysdeps/unix/syscall-template.S:82
#1 0x00403cdd in recv_creds (sock=8, cred=0x7fffe5b0,
v=0x7fffe5af
Hi Serge,
now I started lxcfs within gdb:
(gdb) where
#0 0x7706b610 in __recvmsg_nocancel ()
at ../sysdeps/unix/syscall-template.S:82
#1 0x00403cdd in recv_creds (sock=8, cred=0x7fffe5b0,
v=0x7fffe5af
Hi,
With iptables traffic shaping ?
http://www.szabilinux.hu/bandwidth/
Regards,
Joris
On 09/02/2015 12:11, Alan Hoffmeister wrote:
Hello folks,
Is there a way to limit inbout/outbound netwoork bandwidth? Any tutorials?
--
Alan Hoffmeister
https://twitter.com/alan_hoff
Hi Boudewijn,
Now I have (...) Debian wheezy. it fails with systemd:
(...)
and the nothing happens, I have to use SIGKILL to terminate it.
Am I missing something?
I might be missing the point completely, but is it not just as in
Stéphanes message? Or is your systemd newer than stable?
On Mon, Feb 9, 2015 at 5:11 PM, Dirk Geschke d...@lug-erding.de wrote:
ah, maybe I should try a newer systemd than jessie, jessie
is testing. But this is systemd 215-10, where unstable
uses systemd 215-11. So I did not expect a difference here.
But maybe I should try experimental, this is
Hello folks,
Is there a way to limit inbout/outbound netwoork bandwidth? Any tutorials?
--
Alan Hoffmeister
https://twitter.com/alan_hoff
https://github.com/alanhoff
https://keybase.io/alanhoff
___
lxc-users mailing list
Quoting Christian Brauner (subroutinec...@gmail.com):
Hello,
booting unprivileged ubuntu trusty and vivid container I get the
following messaged when shutting them down:
umount: /dev/zero: block devices are not permitted on filesystem
umount: /dev/urandom: block devices are not
16 matches
Mail list logo
