feraay

Docker enabled? No Problems here with 7.0 and Docker Compose Manager.

Hey, ich muss mich mal wieder an euch wenden komme da nicht weiter. Mein Ziel war es Home Assistant als Container laufen zu lassen. Soweit auch alles super. Wenn ich jetzt aber einen OTBR Container laufen lasse. Dann zerhaut der scheinbar das Routing oder die Netzwerkschnittstellen. Ich komme noch via SSH und Web GUI lokal dran aber 8.8.8.8 ist nicht mehr erreichbar z.b. OTBR soll als priveleged laufen und scheinbar passiert da irgendwas was dann dazu führt das die Außenwelt nicht mehr erreichbar ist. Hier gibt es noch ein paar Besonderheiten: https://community.home-assistant.io/t/ha-docker-with-otbr-docker/735288/19 host system sysctls are set as: $ sysctl net.ipv6.conf.all.disable_ipv6 net.ipv4.conf.all.forwarding net.ipv6.conf.all.forwarding net.ipv6.conf.all.accept_ra_rt_info_max_plen net.ipv6.conf.all.accept_ra net.ipv6.conf.all.disable_ipv6 = 0 net.ipv4.conf.all.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.accept_ra_rt_info_max_plen = 64 net.ipv6.conf.all.accept_ra = 2 Aber das sind alles Sachen über die würde ich mir Gedanken machen wenn das Starten vom OTBR Container auf Network Host nicht mehr dazu führt das der Host keine Verbindung mehr zur Außenwelt hat. In einer VM und auf einem pi hab ich das alles ohne Problem zum laufen bekommen. Folgende Container werden benötigt um Thread in HA abzubilden. HA Matter Server OTBR Matter over Wifi funktioniert dann auch aber Thread sorgt halt dafür das die Kiste kein Internet mehr hat. Ich danke schonmal Vorab für eure Zeit und Hilfe. Falls weitere Infos benötigt werden gern Bescheid geben. Vielleicht hat ja jemand von euch eigene Erfahrungen mit der Thematik. Besten Dank. Grüße

Adding the following to XML seems to work. Cpu is set to host-passthrough <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,level=30,-waitpkg'/> </qemu:commandline> Source

I try to run docker with wsl2 on windows server 2022 vm. when I modify the cpu part the vm does boot with cpu passtrough it only boots into recovery. But even with modified xml docker doesn’t work. so it’s a Linux kernel thing? Intel 13900 no gpu passtrugh

I guess in my case it's some cached stuff from Plex Phototrancoder... not a file I created. /mnt/user/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder Is it a corrupted zfs Filesystem? Or really just a File not utf8 charset ? Everything works as expected no problems except that folder. Maybe I already transferred the file from my old non-ZFS Cache.... I really don't know. I tried a lot of Tips like sed and iconv or how it's called. My last Clue is to move everything "working" away from the cache pool, wipe and move everything back. But I hoped there will be a "smaller" solution.

Hey, I am struggling with my old Plex folder for a while now. After I used spaceinvaderone´s Auto Dataset Script I noticed that the old Plex Folder was not deleted. /mnt/cache/appdata/plex_broken/l/l/p/Cache/1/test# ls -l /bin/ls: cannot access 'f913f438c95d6b8ef55eba5bf40b'$'\202\202\201\210\377\377''9e049e.jpg': Invalid or incomplete multibyte or wide character total 0 -????????? ? ? ? ? ? f913f438c95d6b8ef55eba5bf40b\202\202\201\210\377\3779e049e.jpg I just to want get rid of the folder /mnt/cache/appdata/plex_broken/. Thanks in advance guys

Hey, sorry I am struggling for a while now with my old Plex folder. After I used space invaders Auto Dataset Script I noticed that the old Plex Folder would not be deleted. /mnt/cache/appdata/plex_broken/l/l/p/Cache/1/test# ls -l /bin/ls: cannot access 'f913f438c95d6b8ef55eba5bf40b'$'\202\202\201\210\377\377''9e049e.jpg': Invalid or incomplete multibyte or wide character total 0 -????????? ? ? ? ? ? f913f438c95d6b8ef55eba5bf40b\202\202\201\210\377\3779e049e.jpg I just to want get rid of the folder /mnt/cache/appdata/plex_broken/. Thanks in advance guys

So it’s the expected behaviour that boot fail with xmp enabled ?

Hey, i got a little struggle. My RAM supports 6000mhz and without xmp the clock is set to 4800mhz. so I thought ok enable xmp. I have two options on the ASUs z790 xmp1 and xmp2. With the one I get a KERNEL PANIC - NOT SYNCING VFS: UNABLE TO MOUNT ROOT FS And with the other xmp option I get BZIMAGE CHECKSUM ERROR. I don’t really want to overlock just want to run ram and cpu supported clock speed. when I set ram to 6000mhz without xmp the system boots and with default 4800mhz I have also no problems. would be really thankful for any advice. thank you greetings 🖖

Hey, two of my Containers are only updatable with force Update. I don't know why. One is from the Community Applications added and one from Docker hub. All other Containers work normaly from CA and from Docker hub. I don't understand it. thanks in advance.

disabled Preserve user defined networks and IPv4 custom network on interface br0 (optional) in Docker Settings and its seems the problem is gone now.

Hello, i am have strange network issues a few days now. from inside Docker: root@471259259a65:/# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=7.08 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=118 time=8.46 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=118 time=8.00 ms From 172.16.8.99 icmp_seq=9 Destination Host Unreachable From 172.16.8.99 icmp_seq=10 Destination Host Unreachable from Unraid host: root@Mycroft:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 172.16.8.99 icmp_seq=1 Destination Host Unreachable From 172.16.8.99 icmp_seq=2 Destination Host Unreachable From 172.16.8.99 icmp_seq=3 Destination Host Unreachable from laptop same router PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=8.018 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=7.467 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=7.821 ms ssh to Unraid works. shares are working. WebGuis of Docker apps are accessible. I really don't get it. Started just out of nothing and its not permanent after a few minutes its working again. Completely random. If you need anything just let me know. root@Mycroft:~# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 ether d8:bb:c1:a5:e6:5d txqueuelen 1000 (Ethernet) RX packets 19572 bytes 5635331 (5.3 MiB) RX errors 0 dropped 98 overruns 0 frame 0 TX packets 13595 bytes 6960821 (6.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.16.8.99 netmask 255.255.255.0 broadcast 0.0.0.0 ether d8:bb:c1:a5:e6:5d txqueuelen 1000 (Ethernet) RX packets 18876 bytes 5321146 (5.0 MiB) RX errors 0 dropped 986 overruns 0 frame 0 TX packets 10821 bytes 6778539 (6.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 A Lot of dropped packets on bond0 and br0. mycroft-diagnostics-20221012-1141.zip

It’s kind of funny if you read in the Plex Forum they say since Build 1.28.1 HA is broken because of an Update of Intel IHD driver Plex Forum and for us 1.28.1 is better then 1.28.0 don’t get it.

yes your are right. Working for me too.

with Plex Docker 1.28.0.5999 from yesterday HA enabled and HA encoding enabled I don't get the Problems till now. If I enable HDR Tone Mapping its over. On the second play it dies again 3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:8ed9fff2, in Plex Transcoder [14897] Aug 3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 Aug 3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] Plex Transcoder[14897] context reset due to GPU hang Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for preemption time out Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in Plex Transcoder [19028] Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in Plex Transcoder [19028] Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for stopped heartbeat on vcs0 Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on vcs0 Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to reset chip Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_reset+0x26c/0x290 [i915] Aug 3 14:01:22 Mycroft kernel: [drm:__uc_sanitize [i915]] *ERROR* Failed to reset GuC, ret = -110 Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] Plex Transcoder[19028] context reset due to GPU hang Aug 3 14:01:26 Mycroft kernel: Fence expiration time out i915-0000:00:02.0:Plex Transcoder[19028]:24f0! Aug 3 14:06:30 Mycroft kernel: PMS ReqHandler[17675]: segfault at 0 ip 0000000000000000 sp 000014705a37b1d8 error 14 Aug 3 14:06:30 Mycroft kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. Aug 3 14:06:54 Mycroft kernel: PMS ReqHandler[31743]: segfault at 0 ip 0000000000000000 sp 000014d23a551f48 error 14 in iHD_drv_video.so[14d237853000+1bdf000] Aug 3 14:06:54 Mycroft kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.