Pducharme

Hi, I deciced to move away from the owncloud Docker for multiple reasons. I was looking for a good appliance VM with Owncloud and automated updates, webmin, other enhencements over the official owncloud VM. It's where I found the great site techandme.se. They create and maintain multiple VM appliances; one of them is an "owncloud VM". Getting started 1. Get the "Ubuntu 16.04 main (or mirror) Preinstalled Owncloud (PHP 7.0)" from this site : https://www.techandme.se/pre-configured-owncloud-installaton/ 2. Extract the ZIP or RAR to a folder on your cache drive (or SSD where you want to store the VMs) I suggest : /mnt/cache/VMs/Disks/owncloud/ 3. Logon in SSH to your Unraid box with root and convert the vmdk using this command : qemu-img convert -p -f vmdk -O raw /mnt/cache/VMs/Disks/owncloud/owncloud.vmdk /mnt/cache/VMs/Disks/owncloud/owncloud.img 4. When the conversion is completed, delete the VMDK and other VMware files (*.vmdk, *.vmx, etc) in the /mnt/cache/VMs/Disks/owncloud/ folder and keep only the new "owncloud.img" 5. create a new VM that point to a Ubuntu template. You can use my XML provided below. 7. Boot the VM and follow the Install scripts questions, it's all automated! VM details from my XML : 1 CPU, 2 Core (6 and 7) - change to the core you want to pin 2GB RAM, max 3GB RAM - change to RAM you want, 2GB works fine for me br0 network - give an IP from your router, accessible from the LAN VNC passwd is 'test', keymap is 'fr-ca' - change to what you want 9p Mount: /unraid (point to /mnt/user) Code of the XML : <domain type='kvm' id='4'> <name>Owncloud</name> <uuid>581679d8-547d-5591-e63e-60b274d871da</uuid> <description>Owncloud VM (techandme.se)</description> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Disks/owncloud/owncloud.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/'/> <target dir='unraid'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:2a:5f:99'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-Owncloud/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='fr-ca'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Configuring 9P Sharing (passthrough of Unraid /mnt/user) : 1. Login on the newly build VM using the ocadmin user and the password you setup in the first boot of the VM. 2. become root by typing sudo -i 3. Create the folder /mnt/unraid: mkdir /mnt/unraid 4. type the following command to go inside the fstab file : nano /etc/fstab 5. On the last blank line of file fstab, add the following : unraid /mnt/unraid 9p rw,dirsync,relatime,trans=virtio,version=9p2000.L,posixacl,cache=loose 0 0 6. Quit & save the fstab file (ctrl+x, Yes to save). 7. Reboot the VM. reboot The new sharing should work and in your Owncloud, you should be able to use "External Storage Support" to point a "local" share to the /mnt/unraid/WhateverFolderYouDesire.

I see that error too, but the docker works for me, so I don't really know. I found out that it take about 30sec or 1 minute before the web UI is accessible after a start.

Already did. But I can't download it anymore! My docker compiled OK on Docker.io, but when I try to add it on Unraid, I aways get this message : Can someone try and let me know if it worked for them ? Dont forget to backup the Settings Before! so you can do the restore. Finally, updated and working., now UniFi 5.0.6 available for everyone

Hi, I was thinking of a cheap VDI infrastrastructure using Unraid KVM hypervisor. That would be really useful for Small Business! Is there a possibility to run this on Unraid : http://myvirtualcloud.net/?p=7521 There is a github project page : https://github.com/Seitanas/kvm-vdi That would be a really nice addition to Unraid !

works fine now. Used the Smdion instructions (except that I had to remove a trailing "/").

Hi! Since the last update to PlexPy (they change the connection to a page instead of a Popup), I can't use plexPy behind a reverse proxy anymore... it just doesn't load anything. Any idea ?

On new install, its to have the wizard running when launching the Web gui. On update, it's to let you put back the backup settings you did before updatIng the docker.

I don't have this file, what to do then? You can create the file and just put a single line with the setting I said.

UniFi docker Update. 4.8.18 now in the UniFi docker. 1. Backup your settings using the UniFi docker. 2. Update the docker. 3. Add back the "is_default=true" in the "system.properties" file in the appdata/UniFi folder. 4. Restart the docker and connect to the Web GUI. Wizard is displayed. 5. Select the link in the GUI to restore a backup and then load the file you backed-up.

I just got an email from Code42 that says that on May 16th, they will stop supporting Operating System I have. They send me to a link saying that : Supported Linux using: Kernel version 2.6.32 or later and glibc version 2.9 or later Supported Not Supported Linux Kernel version 2.6.13 or earlier glibc version 2.4 or earlier latest version supported 4.4.1

Hi, I removed the VERSION=plexpass and the /transcode I had previously. I'm a PLEXPASS for Life but now, even if it says there is a new PLEX server available, it never update if I restart the docker. Did I miss something ? Also, the changes said it should ask me to login to PLEX when i'll install the new image and "detect" if I'm a PlexPass customer or not and if so, update automatically... this doesn't work for me. It never ask to "login", nor install the latest version. I'll try using VERSION=latest, maybe that was also required (?) ** EDIT ** Looks like I needed VERSION=latest.

I'll look into it, but I don't have any of that hardware. You'll have to do the testing yourself

I must be missing a step somewhere ... I have done exactly as you have described above, yet I never get the setup wizard. I have deleted the docker and started over from scratch, but the results are the same. What else can I try? I would try : 1. Remove the docker + image from the Unraid Web UI Docker's page (Remove, and choose yes to remove also the image). 2. I will delete the /mnt/user/appdata/unifi-video and /mnt/user/appdata/unifi-video-logs 3. I will add the docker, then i'll just start/stop it. 4. I will create the file "system.properties" with only 1 line, is_default=true 5. I will start the VM and check the web UI of UniFi-Video. Note: Make sure the file you create is named "system.properties", with no other extension (i.e: system.propreties.txt)...

Yes, that's the point of running this docker. No need for their physical NVR at all, it achieve the same.

Me i'm using it with a 720p camera. I have set it to record on movement on a specific location, so it doesn't take a lot of disk space. I don't see it using much of CPU cycle either. Depends if you put 3 camera always recording 24/24, that probably will use lots of space and CPU. Maybe Ubiquiti Networks have that metric. Maybe ask on their forum ?

sorry, there is no data folder. it's under appdata/unifi-video just use any file editor (Notepad++ on PC or Smultron on Mac) and create a file called system.properties in this folder. Just add the is_default=true to it and save it. Restart the docker, you'll have the setup wizard. I updated the UniFi to 4.8.15 yesterday. I updated the UniFi-Video to 3.2.1 3-4 days ago.

super!

You should be presented with the setup. If not, stop the docker, then Connect to your appdata/unifi-video/data fonder and create a system.properties. In it, just a single line : is_default = true Start the docker after and you should have the setup were you create your ADMIN account,

yes! I had help from a guy over at Ubiquiti Networks Forum. I had to add parameters to the startup command that launch the service. Why? I don't know! but it works... Something about a path missing, but it was working up to 3.1.4 version without that. Also, still issues with UniFi Video 3.2 NVR, some camera not recongnize by NVR, also some issue in upgrading for lots of people over at the Ubiquiti Forum. In my opinion, this release of UniFi Video 3.2 is a botched release! They also drop support for AirCam Gen1 cameras, so basically, everyone that update to NVR 3.2 won't be able to use those AirCam. Not great for a company to drop support of perfectly working devices just to drive sales... Anyway, now the Docker works and run the latest NVR, 3.2. Pat

If your AP was previously adopted on another controller, you'll need to set-inform it. I find that I had to manually tell the AP what was the address of the controller. Maybe it's because it reside in a docker (?).

Yes, I did update the docker for Unifi-Video today to 3.2 release, but now, I got an error with starting. I even try deleting the appdata/unifi-video folder, but it seems it doesn't work either. Complaints about : no_ubnt_webrtc_jni in java library path... I'll have to search... for now, it's broken!

Just tried it. Stayed the same (8.2.2). I wonder if I have to delete the config folder too... but i would loose my config

I have the exact same question! Tell us if you figure it out!

very nice!

Thanks! Any way to run on the plexpass version ? I did not read all the thread I'm already running, but not on the plexpass version. ** EDIT ** Forget that stupid question, I set VERSION to plexpass, now have the plexpass version That also fixed my CPU usage issue that the version 6.1.9 brought this morning (that was caused by my aging needo plex Docker.)