JoergHH

Members
  • Posts

    167
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Hamburg/Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JoergHH's Achievements

Apprentice

Apprentice (3/14)

21

Reputation

1

Community Answers

  1. No. It simply didn't work, I didn't pursue the matter any further and I won't either. So it is done for me. Unfortunately.
  2. I am still on 6.9.2 and have the described problem. Unfortunately the patch is not offered to me via the App Store - what now?? I can't update to the current Unraid version at the moment for various reasons.
  3. I just solved it myself. The line in Post Parameters (Advanced View) should read: lame-cleaner --device=cpu --port=8080 --host=0.0.0.0 I read it wrong, dumbass. 🙄
  4. Nope, unfortunately it doesn't work: Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='lama-cleaner' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -p '8081:8080/tcp' -v '/mnt/user/appdata/lama-cleaner/torch_cache':'/root/.cache/torch':'rw' -v '/mnt/user/appdata/lama-cleaner/huggingface_cache':'/root/.cache/huggingface':'rw' 'cwq1913/lama-cleaner:cpu-0.26.1' --device=cpu --port=8080 --host=0.0.0.0 1b3a2a10a0ccbdc36f299a09e534bc0f66a90db7d0bd0b7ad96b0169893332f3 docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "--device=cpu": executable file not found in $PATH: unknown. The command failed.
  5. I am trying to install Lama Cleaner (https://github.com/Sanster/lama-cleaner#docker) in the Docker CPU version, but I am not succeeding. Docker just doesn't want to start. Unfortunately I'm not the Docker expert either, but I suspect it's because of the options --device=cpu --port=8080 --host=0.0.0.0 is the reason. Can someone please help me and tell me what to put where in the template? Before the installation I had created the cache directories under .../appdata/lama-cleaner/.
  6. Is there any way or chance to make step #1 persistent as well?
  7. This means, however, that the Sundtek drivers must be (re)installed every time the container (image AKA app) is updated, right? Because changes in the container are not persistent.
  8. Hmmm, so should I wait with the manual installation of the Sundtek drivers until they have landed in your plugin?
  9. Is the documentation up to date now and may I assume that the whole installation has to be repeated for a Unraid system update?
  10. How about adding the Sundtek drivers to the plugin? Otherwise we are talking about redundancies and that can't be in the sense of Limetech and the users.
  11. I don't understand. The exact opposite is claimed here: https://sundtek.de/wiki/index.php?title=Docker#Unraid
  12. pi:~ $ lsusb ... Bus 001 Device 005: ID 2659:1210 Sundtek MediaTV Pro III (EU) ... pi:~ $
  13. Well, what do you think about a game based on language? 😉 But of course EVERYTHING should be readable in German, i.e. also the GUI. It would be desirable if the config is completely adjustable in /appdata as it is actually the case with almost all Unraid app.
  14. Do the drivers also work if the DVB device is connected via USBIP to a remote system (in my case a Raspberry PI with a DVB-C stick in a room far away)?