[Ltsp-discuss] LTSP on LXD

[Fatih ER]

Hi there friends,



Actually this is a direct question for Stéphane Graber because he is the master of both worlds for me. But any other friendly helps would be appreciated. I’m enjoying LXD recently by following guides of Stéphane to learn how it works. ZFS and Bridged Networking works like a charm.



Started to move my KVM virtual machines to LXD containers for development and I hit a bump on my LTSP Servers.



When I used:



#ltsp-build-client --fat-client --fat-client-desktop ubuntu-desktop --arch amd64 --base /opt/ltsp --chroot amd64-nvidia --skipimage --purge



I got :



mknod: /opt/ltsp/amd64-nvidia/test-dev-null: Operation not permitted

E: Cannot install into target '/opt/ltsp/amd64-nvidia' mounted with noexec or nodev

error: LTSP client installation ended abnormally



Searched the internet whole day and can’t find any tips to follow.



Thanks in advance, and have a great day.

[Stéphane Graber]

Post by Fatih ER
Hi there friends,
Actually this is a direct question for Stéphane Graber because he is the master of both worlds for me. But any other friendly helps would be appreciated. I’m enjoying LXD recently by following guides of Stéphane to learn how it works. ZFS and Bridged Networking works like a charm.
Started to move my KVM virtual machines to LXD containers for development and I hit a bump on my LTSP Servers.
#ltsp-build-client --fat-client --fat-client-desktop ubuntu-desktop --arch amd64 --base /opt/ltsp --chroot amd64-nvidia --skipimage --purge
mknod: /opt/ltsp/amd64-nvidia/test-dev-null: Operation not permitted
E: Cannot install into target '/opt/ltsp/amd64-nvidia' mounted with noexec or nodev
error: LTSP client installation ended abnormally
Searched the internet whole day and can’t find any tips to follow.
Thanks in advance, and have a great day.

You cannot mknod inside unprivileged containers, the kernel just won't let you.

Either you need to work around the problem by moving around a compressed
tarball without the /dev entries and bind-mount the ones from the
container /dev onto them instead, or go the easy way about it and just
make the container privileged with 'lxc config set NAME security.privileged true'.

You'll then most likely hit another restriction which is about mounting
potentially dangerous filesystems in unusual locations which our
apparmor profile blocks. To turn that retriction off, running 'lxc
config set NAME raw.apparmor "mount,"' should do the trick.

Once you've done those two config updates, restart the container and
things will hopefully work fine.

[Valtteri Suojanen]

question if you don't mind:

what is this LTSP on LXD project and what would be the benefit for the
actual clients if booting in same network? or was it just for your R&D
building and maintaining the client chroots? with this little information
it sounds complicated to have multiple virtualization

Do you have a link that would tell us an architechture example, use case
etc ?

Valtteri Suojanen
17.6.2016 10.50 "Fatih ER" <***@eryildiz.com> kirjoitti:

Hi there friends,



Actually this is a direct question for Stéphane Graber because he is the
master of both worlds for me. But any other friendly helps would be
appreciated. I’m enjoying LXD recently by following guides of Stéphane to
learn how it works. ZFS and Bridged Networking works like a charm.



Started to move my KVM virtual machines to LXD containers for development
and I hit a bump on my LTSP Servers.



When I used:



#ltsp-build-client --fat-client --fat-client-desktop ubuntu-desktop --arch
amd64 --base /opt/ltsp --chroot amd64-nvidia --skipimage --purge



I got :



mknod: /opt/ltsp/amd64-nvidia/test-dev-null: Operation not permitted

E: Cannot install into target '/opt/ltsp/amd64-nvidia' mounted with noexec
or nodev

error: LTSP client installation ended abnormally



Searched the internet whole day and can’t find any tips to follow.



Thanks in advance, and have a great day.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports. http://sdm.link/zohomanageengine
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Fatih ER]

@Stephane Graber :

Thank you very much. I hit a bump again.. lxc config set <containerName> apparmor.raw "mount" command doesn’t worked but after a little googling I found a solution (of course you answered someone else on github issues again =) Now It worked like a charm. For the record I want to share the command. Maybe someone else needs it again.

lxc config set <containerName> raw.lxc lxc.aa_profile=unconfined

@Valtteri Suojanen :

LXD is a hypervisor based on Linux containers that provides blindingly fast, very efficient, very low-footprint virtual machines of any Linux on Ubuntu (Excerpt from http://www.ubuntu.com/cloud/lxd <http://www.ubuntu.com/cloud/lxd>) It enables us to make more dense Virtual Machine Hosts with more performance on guests. At production I’m using KVM virtual Machines for my datacenter and LTSP Servers I currently run are guests on this hosts. And after Ubuntu 16.04 release I want to be on edge and started to try ZFS file system and LXD. Most of my Linux guest worked out of the box on LXD and to make it less complicated I decided to keep only windows guest on KVM and move all Linux guests to LXD.