Jump to content

Search the Community

Showing results for tags 'lxd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services


  • drobbins' Blog
  • It's a Bear's life
  • haxmeister's Blog
  • psychopatch's Blog
  • 666threesixes666's Blog
  • decision theory
  • Chris Kurlinski's Blog
  • Sandro's Blog
  • danielv's Blog
  • Not So Stupid Admin Tricks
  • maldoror's Blog
  • andreawilson's Blog
  • Simple Step-by-Step Server Setup
  • saraedward's Blog
  • eusanpe
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






First Name

Last Name



Found 8 results

  1. I have a host that is running Ubuntu and LXD. I've installed a container from public image that is funtoo 1.3. I then did and upgrade to 1.4 for the new container I created. In /var/lib/portage/world there was one entry from the public image /sys-kernel/debian-sources-lts My question is, does a container need to have kernel sources installed? Since it's using the hosts kernel? I do understand that some packages may require kernel sources as dependency, but when the kernel is compiled it can not be installed. Is there a good 'best practices' on what do do with kernel sources within a container
  2. Hello, After sometime emerging emerge -auDN @world xorg-x11 --jobs on container (using funtoo 1.4) x11-drivers/nvidia-drivers-430.26-r2 fails with: * ERROR: x11-drivers/nvidia-drivers-430.26-r2::core-gl-kit failed (install phase): * Can not read .manifest! * * Call stack: * ebuild.sh, line 93: Called src_install * environment, line 5276: Called nv_parse_manifest * environment, line 4438: Called die * The specific snippet of code: * [ -r .manifest ] || die "Can not read .manifest!"; What should I do to proc
  3. Hello, I'm trying to set up a LXD GPU-accelerated container. First time doing so i used https://www.funtoo.org/LXD/GPU_Acceleration but on emerge -auDN @world xorg-x11 --jobs step x11-drivers/nvidia-drivers fails with: * Could not find a usable .config in the kernel source directory. * Please ensure that /usr/src/linux points to a configured set of Linux sources. * If you are using KBUILD_OUTPUT, please set the environment var so that * it points to the necessary object directory so that it m
  4. Hello, where configuration file of LXD/LXC containers is store in Funtoo? According to google that such files, in some other LINUX distributions, are stored in /var/lib/lxc/container/<container>/config or /container/<container>/config, but no such file exists in Funtoo. I'm asking this so I would be able, for example, to change from lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 to lxc.network.type = macvlan lxc.network.macvlan.mode = bridge lxc.network.flags = up lxc.network.link = eth0 Thank you, -- Saulius
  5. Hello, If I''m not mistaked, funtoo hosting is using ZFS. I use LVM all the time, but it seems that users of LXC/LXD more favores ZFS. How stable ZFS in production? Has anybody, from funtoo community, experienced any problems, or data loss with ZFS? Does LVM has some real dowsides comparing to ZFS, in real usage? Has anybody experienced any? It would be interesting to know what storage driver people choose for their LXC/LXD servers? Thank you, -- Saulius p.s. I know there is documentation https://lxd.readthedocs.io/en/latest/storage/
  6. Hi, currently I'm running Funtoo server with several OpenVZ containers. Funtoo moving to LXC/LXD, so I think it's time for me too. The upgrade of the host system to new kernel and LXC/LXD is very straightforward, no questions there. But what is the best way to migrate OpenVZ containers to LXC/LXD? Thank you, -- Saulius
  7. Wouldn't it be nice to have all the virtualization/emulation software in one kit instead it being all over the place? It would make testing and deploying virtualization technologies much easier. Most of the virtualization software is in nokit. LXC and LXD are in core-kit. Some libvirt python bindings are in python-kit, and virtualbox guest additions are in xorg-kit. virtualzation pkgs: app-emulation/libvirt::nokit app-emulation/qemu::nokit app-emulation/lxc::core-kit app-emulation/lxd::core-kit app-emulation/virtualbox::nokit app-emulation/virtualbox-bin::nokit app-emu
  8. I am trying to launch a container with lxd and am not having any such luck. These are the steps I followed: https://wiki.gentoo.org/wiki/LXD 1. install lxd (I did not install criu and will add that for a future build) 2. manually configure kernel for lxd (I didn't do ebuild lxc or ebuild criu) 3. lxd group / user didn't exist, so I created it 4. add myself to that group 5. started lxd 6. initialized lxd (the order on the gentoo website says otherwise, but I couldn't do it in that order) 7. lxd automatically setup the network interface via the lxd service, so I didn't have the n
  • Create New...