- 13 Jan, 2015 4 commits
-
-
Axel Neumann authored
Container fail to start with configs (as shown below) where the same vlan id is used for several type=vlan container interfaces. Then, during the instantiation of the vlan interfaces, an error occurs because the lxc code tries to assign the same temporary name to both of them before it is bound into the container. > lxc.network.type = vlan > lxc.network.flags = up > lxc.network.link = eth1 > lxc.network.vlan.id = 3842 > lxc.network.name = iso0 > > lxc.network.type = vlan > lxc.network.flags = up > lxc.network.link = eth2 > lxc.network.vlan.id = 3842 > lxc.network.name = iso1 Signed-off-by:Axel Neumann <neumann@cgws.de>
-
Serge Hallyn authored
This isn't the perfect fix. In fact close_all_fds shouldn't be stored in the lxc_conf. But this will fix the tests short-term. Signed-off-by:Serge Hallyn <serge.hallyn@ubuntu.com>
-
Serge Hallyn authored
it has unfortunate reprecussions elsewhere, and the needed fix can be done another way This reverts commit 1f76453a.
-
Serge Hallyn authored
Because we never have that any more Signed-off-by:
-
- 12 Jan, 2015 2 commits
-
-
Serge Hallyn authored
Riya Khanna reported that with a ramfs rootfs the mount to make / rprivate was returning -EFAULT. NULL was being passed as the mount target. Pass "/" instead. Reported-by:
riya khanna <riyakhanna1983@gmail.com>> Signed-off-by:
Stéphane Graber <stgraber@ubuntu.com>
-
Serge Hallyn authored
When containers request to be daemonized, close-all-fd is set to true. But when we switched ot daemonize-by-default we didn't set close-all-fd by default. Fix that. In order to do that we have to always have a lxc_conf object. As a consequence, after this patch we can drop a bunch of checks for c->lxc_conf existing. We should consider removing those. This patch does not do that. This should close https://github.com/lxc/lxc/issues/354Signed-off-by:
-
- 10 Jan, 2015 16 commits
-
-
Michael Adam authored
by breaking and shortening some lines. Signed-off-by:
Michael Adam <obnox@samba.org> Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
Michael Adam authored
Signed-off-by:
-
- 08 Jan, 2015 2 commits
-
-
hallyn authored
apparmor: Fix slave bind mounts
-
Martin Pitt authored
The permission to make a mount "slave" is spelt "make-slave", not "slave", see https://launchpad.net/bugs/1401619. Also, we need to make all mounts slave, not just the root dir. https://launchpad.net/bugs/1350947
-
- 05 Jan, 2015 5 commits
-
-
Stéphane Graber authored
Signed-off-by:
-
Stéphane Graber authored
Just like we block access to mem and kmem, there's no good reason for the container to have access to kcore. Reported-by: Marc Schaefer Signed-off-by:
-
Natanael Copa authored
Alpine Linux provides yaml files with latest release instead of the old approach with .latest.txt. Signed-off-by:
Natanael Copa <ncopa@alpinelinux.org> Acked-by:
-
Michael Adam authored
fedora-release has been split into fedora-release and fedora-repos. Signed-off-by:
-
Michael Adam authored
This is to prevent systemd-journald to enter a 100% cpu loop. Signed-off-by:
-
- 19 Dec, 2014 4 commits
-
-
Johannes Kastl authored
lxc-opensuse: Disable building openSUSE containers on 13.2/Tumbleweed only if wrong version of build package is installed Signed-off-by:
Johannes Kastl <git@ojkastl.de> Acked-by:
-
Johannes Kastl authored
Signed-off-by:
-
Serge Hallyn authored
In contrast to what the comment above the line disabling it said, it seems to work just fine. It also is needed on current kernels (until Eric's patch hits upstream) to prevent unprivileged containers from hosing fuse filesystems they inherit. Signed-off-by:
-
Serge Hallyn authored
If a container has a bind mount from a host nfs or fuse filesystem, and does 'umount -f', it will disconnect the host's filesystem. This patch adds a seccomp rule to block umount -f from a container. It also adds that rule to the default seccomp profile. Thanks stgraber for the idea :) Signed-off-by:
-
- 04 Dec, 2014 4 commits
-
-
https://github.com/vlajos/misspell_fixerVeres Lajos authored
Signed-off-by:
Veres Lajos <vlajos@gmail.com> Acked-by:
-
S.Çağlar Onur authored
Signed-off-by:
S.Çağlar Onur <caglar@10ur.org> Acked-by:
-
Shuai Zhang authored
There are now two (permitted) ways to add data to netlink message: 1. put_xxx() 2. call nlmsg_reserve() to get a pointer to newly reserved room within the original netlink message, then write or memcpy data to that area. Both of them guarantee adding requested length data do not overflow the pre-allocated message buffer by checking against its cap field first. And there may be no need to access nlmsg_len outside nl module, because both put_xxx() and nlmsg_reserve() have alread did that for us. Signed-off-by:Shuai Zhang <zs.broccoli@gmail.com> Acked-by:
-
Arjun Sreedharan authored
when waitpid() is interrupted, errno is not set to the negative value -EINTR. It is set to EINTR. check against EINTR. Signed-off-by:
Arjun Sreedharan <arjun024@gmail.com> Acked-by:
-
- 03 Dec, 2014 3 commits
-
-
Stéphane Graber authored
Signed-off-by: -
Shuai Zhang authored
Signed-off-by:
-
Stéphane Graber authored
The previous error message made it look like the host interface name was the concatenation of both the host and guest interface names. Closes #374 Signed-off-by:
-
