Le 13/10/2015 11:49, Fajar A. Nugraha a écrit :
On Tue, Oct 13, 2015 at 4:44 PM, Christian Benke <[email protected]> wrote:
On 13 October 2015 at 11:15, Fajar A. Nugraha <[email protected]> wrote:
So bottom line, don't bother unless you're willing to run a
"frakenstein", unsupported distro. Either retry with stretch and hope
it works better, or switch to ubuntu.
Thanks a lot for the detailed explanation Fajar! Looks like I'm just
going to run privileged containers and hope for the best. Turns out,
doing the testing on the right distribution too is essential :-) (I
tried LXC on my Ubuntu Trusty workstation and deemed it working, but
the server is running Debian Jessie)
Yep, trusty is probably the best distro for host lxc right now.
Particularly if you also add ppa:ubuntu-lxc/lxc-stable to get
lxc-1.1.4 and lxcfs.
Privilged containers on jessie should work, although I'd still
recommend using lxc-1.1.x (either compile from source, or port
ubuntu's package recipe) instead of the bundled 1.0.6
You can run unprivileged Jessie container in a Jessie host. The point is
that the container fails to start mainly because of systemd in the
Jessie container.
To tackle that problem, i create a custom image of Jessie without
systemd and it runs perfectly. I give the details to create the image
and the container in my blog (in french, sorry):
https://www.meseira.fr/blog/post/2015/08/02/unprivileged-jessie-container/
It consists in using the tools of lxc-ci and modifying the script
devoted to Jessie image to replace systemd by sysvinit. After, you just
have to set your cache directory to provide the custom Jessie image to
lxc-create.
Xavier
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
