Jump to content

Search the Community

Showing results for tags 'lxc'.

  • 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
  • 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 5 results

  1. 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 proceed? Is this happening on container only? Thanks in advance
  2. 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 might find .config. * ERROR: x11-drivers/nvidia-drivers-430.40::gentoo failed (pretend phase): * Kernel not configured; no .config found in /usr/src/linux Should I compile a kernel for the container? (manual or genkernel) Or should i use the host .config (debian-sources)?
  3. 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
  4. 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/ but documentation is one thing, and user's experience another... :)
  5. 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-emulation/xen::nokit virtualization tools: app-emulation/virt-manager::nokit app-emulation/virt-viewer::nokit app-emulation/virtio-win::nokit app-emulation/virtualbox-guest-additions::xorg-kit app-emulation/open-vm-tools::nokit dev-python/libvirt-python::python-kit cloud related virtualization software: app-emulation/docker::nokit app-emulation/cloud-init::nokit app-emulation/containerd::nokit hard emulators: app-emulation/bochs::nokit app-emulation/armv8-fast-model::nokit app-emulation/edumips64::nokit app-emulation/vmips::nokit I'm sure I forgot many packages, the open-vz kernel sources, probably more emulators, and more stuff related to docker, but this is just an idea how to consolidate the virtualization packages into one kit.
  • Create New...