callummc

Members
 View Profile  See their activity

  • Posts

    50

  • Joined

  • Last visited

 Content Type 

Posts posted by callummc

    Build new image (IB-gateway)

    in Docker Engine

    Posted

    Give this a try :

    1. Go to unRAID --> Settings --> Community Applications --> General Settings
    2. Find an option labelled "Enable additional search results from dockerHub?", and change the drop down to "Yes".
    3. Click "Apply"
    4. Then click "Done".
    5. Go to unRAID --> Apps and locate the search field (top right hand corner of the Apps page)
    6. Type "ib docker" (no quotes) and click the search button.
    7. You'll be shown a Community Applications (CA) Search Page which states that there was "no matching content found",
    8. Inspect the search page closely however, and you'll see a docker icon/logo in the middle of the page, with a link underneath labelled "Get more results from DockerHub".
    9. Click the link and a short search will be then be conducted on your behalf, resulting in a list of potential apps from the DockerHub.
    10. Select your preferred version, click "Add" and follow the prompts (same as adding a docker from the CA "Apps" section of unRAID)

    Please note that Ryan Kennedy of ryankennedy.io has not published this app on DockerHub (his only public repository is DeepDream - last updated 2 years ago) so the specific code you likned to will not be shown in the search results.

     

    However if I understand your intent correctly, I believe that a search conducted via the community applications "Apps" page will list several dockers for the same "Interactive Brokers" application, essentiually assisting you to achieve the same outcome (getting the IB app running in a docker on unRAID).

     

    A casual inspection indicates that the 5th, or perhaps 8th app, in the search results might be worth a quick look. 

     

    Hope that helps :)

     

     

    • Upvote 1

    Request: Homebridge

    in Docker Engine

    Posted

    14 hours ago, erichner said:

    So for all of you that are having issues with the Homebridge docker quitting after X amount of time (most likely due to the harmonyhub plugin). Try this:

     

    • Edit the docker
    • Turn on Advanced
    • In parameters add:

     

    This should restart the docker if it crashes unexpectedly.

     

    When you referenced :

       --restart=unless-exited

     

    Is there any chance that you meant? 

     --restart=unless-stopped

     

    I attempted your suggestion, however it caused the docker to fail when executing the run command. When I then tried to look the command up online, I couldn't locate it anywhere in the Docker documentation.  A little further digging, and I found the "unless-stopped" reference, which sounds quite similar. 

     

    Not sure if you've made a typo or I've missed something. But as "unless-stopped" does not cause the docker to crash, I've temporarily set it to that for now (docker runs - no problem), and hopefully it fixes the issue described earlier (so far, so good!) :)

    Virtual machine on ASRock FM2A88M-HD+ R2.0 / AMD A10-7850K / HD 5450

    in VM Engine (KVM)

    Posted

    Hi yall,

     

    I'm trying to run up an instance of XBMC in a VM with PCIe passthrough for the video card.

     

    I have the following settings configured under the ASROCK BIOS :

     

    * IOMMU - Enabled

    * SVM (AMD-V) - Enabled

     

    Which results in nice messages being displayed on the info tab in unRAID (Screen Shot 1)

     

    I've got an SSD formatted as BTRFS and mounted using the "Unassigned Devices" plugin, located at /mnt/disks/virtual.

     

    On this disk I've created two folders "filesys" and "iso", where the latter folder contains an image of Kodibuntu titled "kodibuntu-14.0-helix_amd64.iso".

     

    I've configured a VM under the VMs tab, with the following configuration (Screen Shot 2) :

     

    <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>VirtualHelix</name>
  <uuid>a3cf9aa9-f5db-1476-7cae-2659900d1e52</uuid>
  <description>A virtual machine.</description>
  <metadata>
    <vmtemplate name="Custom" icon="ubuntu.png" os="ubuntu"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.3'>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/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disks/virtual/filesys/VirtualHelix/vdisk1.img'/>
      <target dev='hdb' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disks/virtual/iso/kodibuntu-14.0-helix_amd64.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/test/'/>
      <target dir='shared'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:c3:c0:43'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/VirtualHelix.org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/>
  </qemu:commandline>
</domain>

     

    When using OVMF, I get a blank screen (no light, nothing...) but keyboard control appears to be removed from the unRAID host.

    When using SeaBIOS, I get the Kodibuntu install screen appear on the appropriate graphics card, but the USB keyboard does not respond (and appears to have been removed from the host also).

     

    Any suggestions?  I'd really like to get this VM up an running ASAP :P

     

     

     

    Screen_Shot_2015-06-14_at_11_12.26_am.png.056722ac0ce4d308e2d39689343cf947.png

    Screen_Shot_2015-06-14_at_11_25.14_am.png.9637efa4e6364c934dc356fc07e517ee.png

    Minimum Recommended Ram for Docker usage

    in Docker Containers

    Posted

    I know it doesn't exactly answer your question, but I thought I would echo the sentiments NAS expressed earlier on RAM economy.

     

    My initial rig had a stack of apps and 4GB of RAM, but would grind / stutter a bit under heavy load (it's now running 8GB without a hitch).

     

    As a contrast, the new rig I'm toying with runs a Core i5, 16GB RAM and the following docker apps :

     

    • Plex (w/ Transcoding in Ram)
    • Headless XBMC
    • Sabnzbd
    • SickRage
    • CouchPotato
    • Headphones
    • TVHeadEnd
    • Maraschino
    • Transmission
    • WebGrab++
    • DUC

     

    I'm serving up HD streams to 3-4 devices simultaneously, *while* running PAR2 checks, unZIP/unRAR operations and downloading new media streams @ 2-3Mbps in the background.

     

    All of this runs as smooth as butter, using only 3-10% CPU on average.

     

    Grab every bit of RAM you can afford early on.... it makes a considerable difference when running a number of apps. 

     

    You'll always end up adding more apps than you originally intended  ;D

     

    [Deprecated] tobbenb's Docker Template Repository - WebGrab+Plus

    in Docker Containers

    Posted

    I'm having a crack at setting up WebGrabberPlusPlus with TVHeadEnd and a couple of HDHomeRuns.

     

    TVHeadEnd is recognising my HDHR and scanning the channels (Major win! - Woohoo!)

     

    However, I'm a little lost as far as configuring WebGrabberPlusPlus goes.

     

    Has the WebGrab++.config.xml file been pre-configured in some way, or do I need to modify that myself? 

     

    EG. The "Filename" attribute is currently set to "C:\ProgramData\ServerCare\WebGrab\guide.xml", should I change this to reflect the path I entered on the docker config? (like "/data/config.xml")  Or is this automagically managed some other way?

     

    I can also see that the package includes the SiteINI pack... do I need to do anything special to configure this for an AU grabber?

    Sickbeard/ Sickrage web UI won't load

    in Docker Containers

    Posted

    I imagine it should work without a hitch.  A day or so ago, I used your docker config file and changed the repository name from needo/sickrage to adamrbell/sickrage and that worked for me.

     

    If you've mirrored the code change Adam made, it should work for everyone else too.

     

    Can anyone confirm?  (I'm away from my install at the moment or I'd try it myself)

    TVHeadEnd PVR Docker for use with Kodi

    in Docker Containers

    Posted

    Yes - I discovered that you have the drivers installed after checking your docker file in github.

     

    Your question was on the right path.  As the HDHomeRun tuner is a network device, it connects on a specific port (although I'm not sure exactly which one).  I switched the docker app to "host" mode, which then enabled it to recognise the HDHomeRun tuners  8)

     

    I should probably work out which port it connects on and switch it back to bridge mode at some point. Right now I'm busy trying to work out the WebGrab++ config to see if I can get TVHeadEnd up and running  ???

     

    For the moment, I can confirm it recognises the HDHomeRun tuners and enables a channel / mux scan to be completed. 

     

    I'll post more details once I have it all up and running :)

    TVHeadEnd PVR Docker for use with Kodi

    in Docker Containers

    Posted

    I found that it didn't work for me initially either.

     

    I was clicking on the Docker Icon and selecting "WebUI" - I suspect that you might be doing the same thing.

     

    Try going to http://[YourServerIP]:9981

     

    If this works and you can see the TVHeadEnd GUI, then you can make a simple adjustment to your docker container config to set it up correctly.

     

    To adjust the container config :

     

    • Select the "Docker" tab in the unRAID GUI, then click on the TVHeadEnd icon, then select the "Edit" option from the drop down menu.
    • A modal window will then open showing the docker "container config".
    • Move your mouse to the top right hand corner of the modal window, a button labelled "advanced" will appear, allowing you to click on it.
    • Once the "advanced" button has been clicked, you will see additional fields in the "container config" window which were previously hidden.
    • In the field labelled "WebUI", add : http://[YourServerIP]:9981
    • In the field labelled "Icon", add : https://avatars0.githubusercontent.com/u/1908588?v=3&s=400 (This will add a spiffy icon)
    • Click "Apply"

     

    Let me know if that works for you :)

     

     

    TVHeadEnd PVR Docker for use with Kodi

    in Docker Containers

    Posted

    Yeah - I've just updated the container and still no dice :(

     

    From what I understand, TVHeadEnd should show the adaptors... *but* it requires the libhdhomerun software to be installed first.

     

    These are the posts that I've read up on :

     

    https://tvheadend.org/projects/tvheadend/wiki/HDHomerun/5

    https://tvheadend.org/boards/4/topics/14822

     

    Any chance that you could try adding the drivers to the docker image?

     

    TVHeadEnd PVR Docker for use with Kodi

    in Docker Containers

    Posted

    Ok - it seems that I can now get to the TVHeadEnd UI, which is a great step forward :)

     

    But how do I configure my HDHomeRun's here?  I'm not seeing anything under Configuration --> TV Inputs --> TV Adaptors.  I have two HDHomeRun devices on my network, but they don't seem to be appearing and I don't have an option to "add" them?

     

    P.S.  You should consider creating a Docker template repo for this, adding an icon and configuring the "WebUI" link to open to the appropriate page :)

     

     

    Marvell Sata controller with VT-d

    in Virtual Machines - Xen

    Posted

    I recently experienced this issue with an SSD on a new system.

     

    Motherboard : Asrock Z97 Extreme4

    SSD (M.2 Slot) : Plextor PCIe M.2 2280 (PX-G256M6e)

     

    The Plextor SSD utilises the Marvell 88SS9183-BNP2 Native PCIe 2.0 Controller, as do the 128GB and 512GB versions (PX-G128M6e and PX-G512M6e respectively).

     

    Initially, the drive just didn't appear in the Web UI while unpleasant messages appeared in the system log :

     

    EG

    ata5.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)

     

    After much poking around, I finally found this topic and quickly disabled VT-d in the BIOS.  After confirming that my errant drive was finally showing in Dynamix, I followed the solution and have not experienced further issues.

     

    SSDs are gaining traction as cache drives and M.2 slots are appearing on motherboards more frequently - so I thought it would be worthwhile mentioning the Plextor issue to save others the hassle.

     

    Sorry for bumping up an old topic :)