Banuseka

Members
  • Posts

    22
  • Joined

  • Last visited

Everything posted by Banuseka

  1. HI, any chance this docker gets updated to also support GPU integration for motioneye to use?! Best, banuseka
  2. OK port change is working on bridge mode, but not custom... anyone has an idea why?
  3. Hi, unfortunately I am not able to get MeTube running on any other port than 8081. Changing the port in the template simply doesn't work. Can anyone second that behavior? I have MeTube running on its own IP (meaning: "network type: Custom: br0") Best, Banu
  4. Another addition would be to start/stop/restart a docker from the GUI
  5. HI I can second this, except. it only boots up ervey now and than. once I got my 2nd gpu to be passed through to my win10 vm (gtx 1050TI (GV-N105TD5-4GD) on a x8sil-f). but now the server doesnot want to boot properly anymore... (m on unraid 6.9.0-rc2)..
  6. Yh, thx! Figured that as well:) luckily my switch supports LAG and the modes:)
  7. Good call ! Now switched to Bonding (balanced-rr). guess this is better. THX for the advice!
  8. I got it figured !!! I have two nics on my mobo and couln't get "remote tunneled access" to work (no internet, no local access, just some in/out/ data but no handshake) with root@Tower:~# ip route default via 192.168.2.1 dev br1 10.253.0.2 dev wg0 scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 172.18.0.0/16 dev br-8352ee8270e2 proto kernel scope link src 172.18.0.1 linkdown 192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.200 192.168.2.0/24 dev br1 proto kernel scope link src 192.168.2.201 i found that my main IP of unraid that I forwarded the UDP port to was not in use by wireguard, but the second IP I had. Thus I just switched the portforwarding from the main IP to the secondary IP and now everything ist working like a charme. Best, Banu
  9. I already use a redis docker for nextcloud, and NC wants to use redis with a password. that was my intention instead of setting up a second redis docker I'll prob. go for a feature request. Best, Banu
  10. HI @Flight777 can you advise on how to pass a password to a password-protected redis docker? Best, Banu
  11. OK tried to reinstall... now everything woks but obviously have to reconfigure.... for some reaseon port 8080 does not allow me to connect, so had to change that.
  12. I removed and installed it several times, and than suddenly it worked again... Dunno why but it is working now since couple of weeks.
  13. I will just try to reinstall the docker and backup the config this time
  14. nextcloud me now tells that ist would need a pwd to access redis but i havn‘t set one in nextcloud or redis itself. how can i set a pwd in the redis container? best, Banu
  15. hmm i just found that even my wohle config is gone. non of my installiert modules are in the modules folder, and the configfile is a default one...
  16. Hi ich777, I suddenly have troubles having magicmirror2 start. the following is frm the latest log: 0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'server' ] 2 info using npm@6.14.6 3 info using node@v12.18.4 4 verbose config Skipping project config: /magicmirror2/.npmrc. (matches userconfig) 5 verbose run-script [ 'preserver', 'server', 'postserver' ] 6 info lifecycle magicmirror@2.14.0~preserver: magicmirror@2.14.0 7 info lifecycle magicmirror@2.14.0~server: magicmirror@2.14.0 8 verbose lifecycle magicmirror@2.14.0~server: unsafe-perm in lifecycle true 9 verbose lifecycle magicmirror@2.14.0~server: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/magicmirror2/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 10 verbose lifecycle magicmirror@2.14.0~server: CWD: /magicmirror2 11 silly lifecycle magicmirror@2.14.0~server: Args: [ '-c', 'node ./serveronly' ] 12 silly lifecycle magicmirror@2.14.0~server: Returned: code: 1 signal: null 13 info lifecycle magicmirror@2.14.0~server: Failed to exec server script 14 verbose stack Error: magicmirror@2.14.0 server: `node ./serveronly` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 14 verbose stack at EventEmitter.emit (events.js:315:20) 14 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 14 verbose stack at ChildProcess.emit (events.js:315:20) 14 verbose stack at maybeClose (internal/child_process.js:1021:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) 15 verbose pkgid magicmirror@2.14.0 16 verbose cwd /magicmirror2 17 verbose Linux 4.19.107-Unraid 18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "server" 19 verbose node v12.18.4 20 verbose npm v6.14.6 21 error code ELIFECYCLE 22 error errno 1 23 error magicmirror@2.14.0 server: `node ./serveronly` 23 error Exit status 1 24 error Failed at the magicmirror@2.14.0 server script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ] Can anyone help out here? FYI: nothing has been updated, just other containers have been deployed to unraid. Best, Banuseka
  17. make ist easy... max2play, volumio, picoreplayer, squeezelite I guess those are the most used ones out there. best, Banu
  18. OK something is strange... first the server.py is missing, now I had to change "/deem/deemix Music" to "/deem/Music", the server.py is back and deemix is working again. However, I have to do the renaming again after every restart of the container... can someone second this?
  19. when i check for updates in the version tab it says „not available“. even a removal and new install did not do the trick...
  20. Hi all, suddenly my deemix is not working anymore.... the log says the following: [services.d] Starting with ARL python3: can't open file '/deemix/server.py': [Errno 2] No such file or directory ./run: line 6: cd: /deemix: No such file or directory over and over again. anyone hass an idea how to fix this ?? best, banuseka
  21. Hi @dlandon, i want to passthrough an audio device to use the wavein plugin. My device is located at /dev/bus/usb/002/004. However, with the extra prarameter—device=/dev/bus/.../:/dev/bus/002/004 the device doesn‘t show in in the docker... any advice on how to achive this? BTW. the device is a „Behringer UFO202“ to capture audio to send my vinyls around my house. Fot the wavein plugin it needs to be added as favorite with something like „wavin:plughw:1“ bit therefore one has to use „arecord -l“ to identify the correct device. Any help is very much appreciated!!