dnoyeb

so, just got done watching a full movie on the vm... 3 or 4 times throughout the movie the audio would go completely out while the video kept going; then it would all sync up and keep going. this is after adding the mentioned setting to the config file... any other ideas?

gotcha... Total side note... In your guide you have /ext setup to hit a drive you have mounted via unassigned devices... I am trying to do the same thing but it's not showing up (I just reinstalled both dockers so it's back down on 4.3 for now) Does the external drive need to be formatted anything in particular? I think mine is NTFS from windows usage...

That’s because the CrashPlan Docker has auto updated itself to 4.4.1 and the CrashPlan Docker Desktop doesn’t. ok... so.... is there a fix?

I just wish I knew why the docker desktop won't work anymore... just sits at "upgrading..." and shows version 4.3.0. I had this working fine until a recent reboot... Thu Oct 1 14:49:16 CDT 2015 : Restarting CrashPlan Backup Engine Thu Oct 1 14:49:16 CDT 2015 : Starting using /etc/init.d/crashplan... upgrade.sh: line 30: /etc/init.d/crashplan: No such file or directory Thu Oct 1 14:49:16 CDT 2015 : New CrashPlan Backup Engine: root 45 43 36 14:49 ? 00:00:05 /usr/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -classpath /usr/local/crashplan/lib/com.backup42.desktop.jar:/usr/local/crashplan/lang com.backup42.service.CPService Thu Oct 1 14:49:16 CDT 2015 : Exiting upgrade script That's what shows up in the log folder in the config folder.... looks like it's trying to upgrade and cannot...

any headway on getting this working again? Had it working fine until I rebooted my docker today and then the desktop part sat at "upgrading" forever... the screen went away and now when I try to launch it says it cannot connect to the engine (same stuff discussed on the previous two pages).

watched my first movie just now... had a good bit of jitter from time to time, would happen about every 20 minutes or so. Video playback was fine but audio would freak out. Hopefully it's a setting I can change in the config files somewhere... Update: Added options snd-hda-intel enable_msi=1 to my sound.conf file in the config folder of the VM I built and it seems to have fixed the jitters on trueHD so i'm hopeful it fixed the random issues mentioned in the paragraph above... will need to watch a movie tomorrow to confirm.

So I found some example xml's from johnodon in his PXE boot thread and managed to get Openelec beta 5 installed through the Ubuntu live boot cd mode... Strangely enough, passthrough audio is working fine for me with the full install vs using the beta 3 from Limetech where it would not work and menu sounds caused clicking noises galore (yes I tried the fixes mentioned in this thread, no help). Not sure if there is just some stuff in the full version that's not in the forked version. Anyways, i'm going to watch some stuff and see how it works out... If anyone else out there is having issues, I recommend checking out johnodon's pxe thread and look at his xml... I found that every time i edited the VM in the webgui I would have to re-edit the xml and change out ALL the lines of code for the disk controller (from <disk> to </disk> and change the nic from the virtio to e1000.

That was it, I was putting it on the repository field as it shows on the first post... guess the location changed at some point where it needed to be. Moved it to extra parameters and the webgui is back, thanks!

http://[iP]:[PORT:8080]/ .. tried it on the Sabnzb, plex, unifi-video ones... all of them do the same thing. Side note, soon as I remove the cpu flag, it comes right back... so weird I went ahead and put something besides the default in there and still don't see an option for webui.. https://192.168.2.51:9080 is what I put in for Sab ..

Using 6.1.2, applying --cpuset-cpus=4,5 to one of my dockers and while it looks like yes, it is working... There is a side effect. I cannot hit the view webgui anymore from the docker page. That option is simply gone now... Can anyone confirm this / know what it is doing? Here's an example: --cpuset-cpus=4,5 pducharme/unifi-video-controller however it happens on any container I put a --cpuset-cpus= on.

not sure I follow, what are you asking me to look at? The unifi video server shows the right stuff, saves all the cameras etc, they just show disconnected.... then when I login to them they think the server is on some other subnet... almost like when the docker starts up for unifi video; the app thinks its ip is some ip that it isn't and tells the cameras its new IP.

for some reason if I reboot the unraid server and reload the docker; all of my Unraid cameras say disconnected... when I login to them they all say their camera server is something on the 172.17.0.x network which isn't even one of my subnets... I can manually overwrite this and save it; the camera comes back. Works until I reboot again... Any words of wisdom?