Jump to content
funtoo forums

Search the Community

Showing results for tags 'lxc'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


Location


Interests

Found 3 results

  1. 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
  2. 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... :)
  3. 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.
×