- 04 Dec, 2019 1 commit
-
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
- 03 Dec, 2019 6 commits
-
-
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
dongxinhua authored
Signed-off-by:dongxinhua <dongxinhua@huawei.com>
-
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by:
-
- 02 Dec, 2019 33 commits
-
-
Christian Brauner authored
This causes compilation failures due to a bad cherry-pick. Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Signed-off-by: -
Christian Brauner authored
Add a bpf-based device controller implementation. Signed-off-by: -
LiFeng authored
Signed-off-by:LiFeng <lifeng68@huawei.com>
-
Balázs Póka authored
Signed-off-by:Balázs Póka <poka@idata.hu>
-
Rachid Koucha authored
"above" was used instead of "below" Signed-off-by:Rachid Koucha <rachid.koucha@gmail.com>
-
Christian Brauner authored
BugLink: https://bugs.launchpad.net/bugs/1848587 The latter device has been removed apparently. Signed-off-by:
-
Fabrice Fontaine authored
Commit 3b5a0eeb reverted 3aa72711 resulting in lxc being unable to be built on toolchain without SSP support Fixes: - http://autobuild.buildroot.org/results/57945f54ffbc5c8764b6891a4516c4907e56ab97Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com>
-
Aaditya Murthy authored
Fixed the documentation to say that cgroupv2 uses a unified hierarchy Signed-off-by:Aaditya Murthy <amurthy123@utexas.edu>
-
Christian Brauner authored
Closes: https://github.com/lxc/lxd/issues/6408Signed-off-by:
-
Christian Brauner authored
Signed-off-by: -
Serge Hallyn authored
Signed-off-by:Serge Hallyn <shallyn@cisco.com>
-
Florian Margaine authored
lxc2 broke this feature for lxc-execute, and lxc3 broke it for lxc-attach. This adds a test making sure we don't do the same mistake a third time. Signed-off-by:Florian Margaine <florian@platform.sh>
-
Wolfgang Bumiller authored
Callers expect a NULL on error, and with PR #3171 marking the pointer as __do_free, we now return a pointer to freed memory here otherwise. Signed-off-by:Wolfgang Bumiller <w.bumiller@proxmox.com>
-
Christian Brauner authored
Signed-off-by: -
Patrick Havelange authored
In case the internal memfd_create has to be used, make sure we don't clash with the already existing memfd_create function from glibc. This can happen if this glibc function is a stub. In this case, at ./configure time, the test for this function will return false, however the declaration of that function is still available. This leads to compilation errors. Signed-off-by:Patrick Havelange <patrick.havelange@essensium.com>
-
Thomas Parrott authored
Partially reverts 65b92ea5 so that trying to destroy a non-existent container gives an error message. Signed-off-by:
Thomas Parrott <thomas.parrott@canonical.com>
-
KATOH Yasufumi authored
Update for commit 767bd70aSigned-off-by:
KATOH Yasufumi <karma@jazz.email.ne.jp>
-
Rachid Koucha authored
When calling "man lxc.container.conf", an internal "man" keyword is displayed : $ man lxc.container.conf [...] lxc.mount.entry Specify a mount point corresponding to a line in the fstab format. Moreover lxc supports mount propagation, such as rslave or rprivate, and adds three additional mount options. optional don't fail if mount does not work. create=dir or create=file to create dir (or file) when the point will be mounted. relative source path is taken to be relative to the mounted container root. For instance, dev/null proc/kcore none bind,relative 0 0 .fi <-----------------------------------UNEXPECTED KEYWORD !!!! The problem seems to come from the missing blanks before "dev/null proc/kcore none bind,relative 0 0" Moreover, for homogeneity purposes, it is better to use the "programlisting" tag used in the rest of the text instead of "screen". Signed-off-by: -
KATOH Yasufumi authored
Update for commit 0684250fSigned-off-by:
-
Caio B. Silva authored
Signed-off-by:Caio B. Silva <caioboffo@gmail.com>
-
Lukas Jelinek authored
Signed-off-by:Lukas Jelinek <lukas.jelinek@nic.cz>
-
Caio B. Silva authored
Signed-off-by: -
Christian Brauner authored
In the usual case the child runs in a separate pid namespace. So far we haven't been able to reliably set the pdeath signal. When we set the pdeath signal we need to verify that we haven't lost a race whereby we have been orphaned and though we have set a pdeath signal it won't help us since, well, the parent is dead. We were able to correctly handle this case when we were in the same pidns since getppid() will return a valid pid. When we are in a separate pidns 0 will be returned since the parent doesn't exist in our pidns. A while back, while Jann and I were discussing other things he came up with a nifty idea: simply pass an fd for the parent's status file and check the "State:" field. This is the implementation of that idea. Suggested-by:
Jann Horn <jann@thejh.net> Signed-off-by:
-
Christian Brauner authored
Signed-off-by: -
Alban VIDAL authored
Signed-off-by:Alban VIDAL <zordhak@debian.org>
-
