bmullan
commented
8 years ago Uwe..
I tried to find an email to send this to you but failed to locate a working one so I will post it here as part of this "issue"...
I happened on your GitHub repo for: https://github.com/ustuehler/lxc-desktop
As you are probably aware by now although it uses LXC the new LXD has a totally new/different CLI syntax and a JSON api to manage/provision LXD containers both locally & remotely.
Your LXC-DESKTOP appears to be formed around the older style LXC syntax & config info (I called that "legacy" lxc).
Have you given any thought to updating lxc-desktop for LXD?
I learned quite a bit about PulseAudio when building some of my own scripts for LXD and learned about the many challenges with getting it to work in LXD/LXC containers.
I end up using PulseAudio's TCP module capability.
I was wondering if you were still interested in pursuing your LXC Desktop capability but modernizing it to LXD ?
If so I could try to help. I am not much of a programmer anymore (some python & bash) but more of an integrator. However, I think you can see from the Scripts etc on my GitHub (https://github.com/bmullan/CIAB-Guacamole-Remote-Desktop) that I might be able to help collaborate with you on the effort. Let me know (bmullan.mail@gmail.com)
I've just recently found 2 bits of information that I think could solve your lxc-desktop sticking point regarding "device cloning script which runs at container startup" in the new LXD environment.
#1 was this post by someone named - Simon Poirier (simpoir): https://github.com/lxc/lxd/issues/2003
I tried Simon's LXD "lxc launch" example using "-c raw.lxc="lxc.hook.pre-start" and it worked on LXD as his post indicated !
So I thought perhaps that was a good example of how to solve the problem of getting a pre-start script to run on LXD.
#2 was a blog I ran across https://bigjools.wordpress.com/2016/07/13/webex-using-ubuntu-lxd-containers/
Although "bigjools" blog post use-case was about getting webex to work in LXD his 2 examples of how to map Host audio/sound and video devices into LXD worked for me on my system using aplay & vlc to test audio/video.
The only additional step I had to take on my system for the audio/sound to work was mentioned in a previous post on "legacy" lxc by bigjools (the author) where he said:
Now, we can test the sound to make sure that the config worked, try something like this:
aplay /usr/share/sounds/alsa/Front_Center.wav
If you hear the test sound, then it’s all good. If you don’t hear it, and get an error, then you’ll have to Google. In my case, the command was working without any error but there was no sound. I fixed this by adding a custom .asoundrc in the ubuntu user’s home directory:
pcm.!default { type plug slave.pcm { type hw card 1 device 0 } }
defaults.ctl.card 1
It’s highly likely you may have to edit this for your sound hardware, but then again it may work. I’m not an ALSA expert, do some Googling if there’s still no sound, you just need to find the right device. You can test more quickly with a line like this:
aplay -D plughw:1,0 /usr/share/sounds/alsa/Front_Center.wav
Vary the device numbers of 1,0. Hopefully you’ll get it working eventually.
So I just created a ~/.asoundrc for my userID (or use it in /etc/asound.conf) in the LXD container and coupled with his steps in the above LXD blog post (modified to match my system;s /dev/snd devices) ... sound worked well!
Anyway... I think using the combination of info in #1 and #2 above coupled with an updated for LXD version of your lxc-desktop should be workable.
That would only leave the effort of creating an lxd template for it which I have no experience with but I would think someone from the lxc-users@lists.linuxcontainers.org might be interested in assisting?
FYI... I started a new sub-reddit /r/lxd dedicated to LXD as it enabled separation from the "legacy" lxc topics posted in the older sub-reddit /r/lxc
naisanza
Title asks the question Thanks