joelones

Thank you for your help anyway.

Thanks for the help. tried recreating / removing the custom network a bunch of times, whenever I set the driver to macvlan it doesn't appear in the gui...why it does it for some dockers on the same custom network and not others is a real mystery

How does one recreate the custom network? I think my 192.168.10.1/25 network br1.10 was automatically created when I created a bridge on eth1 with a specific VLAN. I tried using the UI to uncheck the docker network (restarted) and then recreate it, not sure if this is the right way (see screenshot) but it did not change anything.

No they don't. Makes no sense to me. I did a normal downgrade via the UI, no dice. Then I actually took a backup of the USB before I started and overwrote the UNRAID USB and still the same. So confused

I'm also experiencing this after installing 6.12.11 for some reason: help?

Just upgraded to 6.12.11 and now some of my IPs for docker on a custom network don't show in the GUI and link goes to about:blank#blocked. Can someone please shed some light here? Why it is all of a sudden happening to some but not all customer IP containers ? Deleting the docker.img and containers does nothing.

I'm still on 6.12.3 and would like to upgrade but facing multiple issues upon trying 6.12.6. Any guidance would be appreciated. The Intel GPU CometLake-S GT2 [UHD Graphics 630] fails to load upon bootup thus the Jellyfin docker fails to start as it is used for gpu transcoding My Windows 10 VM with a pass-through nvdia quadro fails to start All is fine on 6.12.3. Thoughts? clarabell-diagnostics-20231206-1504.zip

I'm trying to the new UniFi Network Application container and getting a tomcat 404 error using a custom bridge setup. Previous container works well with this setup. Can anyone please advise (unraid 6.12.3)

Just tried it again today, same issue same call trace

No I reverted back to 6.12.3 which is working fine. I would add this as the following: mkdir -p /boot/config/modprobe.d echo "options i915 enable_fbc=1 enable_guc=3" > /boot/config/modprobe.d/i915.conf mkdir -p /boot/config/modprobe.d echo "options i915 enable_dc=0" > /boot/config/modprobe.d/i915.conf what does this do? for 6.12.3, no need to add the modprobe lines, it just works. odd

Apparently `/dev/dri/*` which I pass into the jellyfin docker does not exist. root@clarabell:/boot/config# intel_gpu_top -L No GPU devices found Tried this, but modprobe just hangs: mkdir -p /boot/config/modprobe.d echo "options i915 enable_fbc=1 enable_guc=3" > /boot/config/modprobe.d/i915.conf Here is the diagnostics: root@clarabell:~# lsmod | grep intel intel_rapl_msr 16384 0 intel_rapl_common 24576 1 intel_rapl_msr intel_powerclamp 16384 0 kvm_intel 282624 4 iosf_mbi 20480 2 i915,intel_rapl_common kvm 983040 1 kvm_intel crc32c_intel 24576 2 ghash_clmulni_intel 16384 0 aesni_intel 393216 0 crypto_simd 16384 1 aesni_intel cryptd 24576 2 crypto_simd,ghash_clmulni_intel intel_cstate 20480 0 intel_gtt 24576 1 i915 agpgart 40960 2 intel_gtt,ttm intel_uncore 200704 0 intel_pmc_core 49152 0 clarabell-diagnostics-20230912-1149.zip

Are users having problems loading the intel quick sync drivers with 6.12.4? I seem to have to revert back to .3 to get intel quick sync working in my container.

Just install 6.12.4 and can't start jellyfin due to what i think is missing intel drivers??!! Is there a package app for this now with 6.12.4? .3 didn't have this problem

Seems like a power cycle brought back the nic's activities LEDs, not sure what happened. could be I'm on an old (currently overloaded) UPS so maybe power issues, i hope not hardware.

Here's a picture of the nics, the right one is passthroughed to pfsense and the left one is all of a sudden giving me a problem.