Ahmed

I just noticed i can't run an update using the updater.phar anymore. docker exec -it nextcloud updater.phar OCI runtime exec failed: exec failed: unable to start container process: exec: "updater.phar": executable file not found in $PATH: unknown anyone else having this issue? im on v27 docker exec -it nextcloud occ -V Nextcloud 27.0.0

just in case this helps anyone else. I realised when i was testing this, i had put the iommu=pt but only for the boot without gui. When I first tested this it failed and no disk were shown and it was only because i didn't append it to the end of the gui boot line e.g. default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot iommu=pt label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui iommu=pt So essentially you will need to add it to all the boot options if you want the disks to be shown. Or you can just manually add it if you are not running it headless.

awesome - will give that a go then. thanks heaps.

will this work for: Marvell Technology Group Ltd. 88SE9230 01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] (rev 11)

Not 100% sure this is going to work properly and im sure there's prob a better way to do this.. i just wrote up a super amazing script to export the data into influxdb #!/usr/bin/env bash #set -x RAW=$(/usr/local/bin/corsairmi) OUTPUT=/mnt/user/appdata/telegraf/corsair-telegraf.csv function simple() { # echo $(echo "$RAW" | grep "$1" | cut -d ':' -f2 | cut -d ' ' -f 2) echo "$RAW" | grep "$1" | tr -s ' ' | cut -d ':' -f 2 | cut -d ' ' -f 2 } function rail() { # echo "$RAW" | grep -A 3 "output ${1}v" | grep "$2" | tr -s ' ' | cut -d ' ' -f 2 echo "$RAW" | grep "$1" | grep "$2" | tr -s ' ' | cut -d ' ' -f 3 } temp_0=$(simple "temp1") temp_1=$(simple "temp2") powered=$(simple "powered") uptime=$(simple "uptime") supply=$(simple "supply volts") total_watts=$(simple "total watts") # 12V Rail volts_12v=$(rail "output0 volts") amps_12v=$(rail "output0 amps") watts_12v=$(rail "output0 watts") # 5V Rail volts_5v=$(rail "output1 volts") amps_5v=$(rail "output1 amps") watts_5v=$(rail "output1 watts") # 3.3V Rail volts_3_3v=$(rail "output2 volts") amps_3_3v=$(rail "output2 amps") watts_3_3v=$(rail "output2 watts") # InfluxDB output echo "power_supply temp_0=\"$temp_0\",temp_1=\"$temp_1\",total_time=\"$powered\",uptime=\"$uptime\",supply_volts=\"$supply\",total_watts=\"$total_watts\",12v_volts=\"$volts_12v\",12v_amps=\"$amps_12v\",12v_watts=\"$watts_12v\",5v_volts=\"$volts_5v\",5v_amps=\"$amps_5v\",5v_watts=\"$watts_5v\",3.3v_volts=\"$volts_3_3v\",3.3v_amps=\"$amps_3_3v\",3.3v_watts=\"$watts_3_3v\"" > $OUTPUT WIth the output file you can import it straight to influxdb with a cron job to run for like every 5min. Here is how i did it manually # curl -i -XPOST 'http://influxdb-ip:8086/write?db=telegraf' --data-binary @/dir/of/corsair-telegraf.csv HTTP/1.1 204 No Content Content-Type: application/json Request-Id: fd24688f-5c64-11ea-93c0-7085c242ccc6 X-Influxdb-Build: OSS X-Influxdb-Version: 1.7.10 X-Request-Id: fd24688f-5c64-11ea-93c0-7085c242ccc6 Date: Mon, 02 Mar 2020 09:05:40 GMT and now i have to figure out how to get grafana to show the results. fun times!! ***ok scratch that. it didnt seem to work...... seems like it wont input the results even though they appear to be clearly showing in the file.

Thats exactly what i was thinking and was hoping for an answer.

all good. so just adding a variable with the location of the config file in appdata is all it needs. sweet.

Can you please explain where you found the conf file? i did a search and can find it under /var/lib/docker/btrfs/subvolumes/ but i dont think that would be the usual place holder for docker configs. Usually as itimp stated its under /mnt/user/appdata/docker/blah

Ok - ignore that ^^ its working fine.. just has a whole bunch of forbidden's and then it starts working - AWESOME> thanks

So i noticed you have to have an account created to actually test out bbc iplayer via the web. I have firefox setup to pass through privoxy and it works fine. When I start this docker, it fails when it goes to download the show: 2018-12-19 12:37:31,057 DEBG 'get-iplayer' stdout output: ERROR: Failed to download URL (3/3): https://vod-hls-uk-live.akamaized.net/usp/auth/vod/piff_abr_full_sd_ad/bc93a0-b0bsqzq1/vf_b0bsqzq1_18dd5df3-b811-4b90-823d-526d62850072.ism.hlsv2.ism/vf_b0bsqzq1_18dd5df3-b811-4b90-823d-526d62850072.ism.hlsv2.m3u8?__gda__=1545215848_543fe08296c477c872ae1594981a858e ERROR: Response: 403 Forbidden ERROR: Ignore this error if programme download is successful Any suggestions? going to the link via browser i get the "Access Denied You don't have permission to access blah blah " Which makes me think its looking for authentication before it will allow me to dl using this app? So does this docker work without a user login to bbc iplayer?

Hey @JonMielIV - so when you edit the config for this container, you just click on the 'Add another Path, Port, Variable, Label or Device' then add they new variables in and start the docker. When you start up this docker, you can watch the logs to see it go through the proxy you setup in deluge (which has privoxy included). Just make sure you have set that up and the proxy (privoxy) is working properly. If you haven't got deluge setup with privoxy then you will obviously need to get that sorted first. On another note - I also noticed the VPN service provider I'm using is geoblocked (PIA) so no BBC for me until I get another VPN provider.

Ok ok ... figured it out - just needed to add a variable to add the proxy.

Unless I’ve miss understood - anyone around that can help me ?

Hi - thanks for the docker but I am not exactly sure how to get it to work with privoxy. I have privoxy working and connected to London. How do I point this docker to work through privoxy? Sorry for the newbish question (and I see its sort of been answered on page 1 of this thread - but it doesnt explain how to actually do it). Thanks in advance!!

Thanks for your patch - works fine now. Also I left it as the IP as it was the default config from PIA - so i didnt bother. Cheers for the advice.