-
JoergHH started following Could not start Lama Cleaner Docker (https://github.com/Sanster/lama-cleaner) , VirtioFS Support Page , [SUPPORT] Orbital Sync and 1 other
-
[SUPPORT] Orbital Sync
Great project, runs excellently - many thanks! But I wonder why there is no Docker icon. The .svg graphic is linked in the settings, but unfortunately Unraid can't do anything with it :,-( Anyway... I have made a suitable .png in the format 512 x 512, see attachment. Or you can use the online version: https://i.imgur.com/2WuVtUt.png
-
Anyone got Idrive working on Unraid ?
Since I also have problems with the renofischa docker, I switched to snorre0815. It seems to work better as it is the latest IDrive version 3.2.0: https://hub.docker.com/r/snorre0815/idrive-docker/
-
JDownloader: Links/Downloads direkt zum Docker im eigenem Netzwerk pipen?
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.
-
all docker containers lists version “not available” under update
Done and works as expected.
-
all docker containers lists version “not available” under update
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.
-
Could not start Lama Cleaner Docker (https://github.com/Sanster/lama-cleaner)
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. 🙄
-
Could not start Lama Cleaner Docker (https://github.com/Sanster/lama-cleaner)
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.
-
Could not start Lama Cleaner Docker (https://github.com/Sanster/lama-cleaner)
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/.
-
[Plugin] DVB-Driver
Is there any way or chance to make step #1 persistent as well?
-
[Plugin] DVB-Driver
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.
-
[Plugin] DVB-Driver
Hmmm, so should I wait with the manual installation of the Sundtek drivers until they have landed in your plugin?
-
[Plugin] DVB-Driver
Is the documentation up to date now and may I assume that the whole installation has to be repeated for a Unraid system update?
-
[Plugin] DVB-Driver
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.
-
[Plugin] DVB-Driver
I don't understand. The exact opposite is claimed here: https://sundtek.de/wiki/index.php?title=Docker#Unraid
-
[Plugin] DVB-Driver
pi:~ $ lsusb ... Bus 001 Device 005: ID 2659:1210 Sundtek MediaTV Pro III (EU) ... pi:~ $