Unraid OS version 6.12.4-rc18 available

The Docker Area in Dashboard is very slow with 6.12.4RC18 . Doesn't matter if you using the folderview plugin or not. @alturismo got the same.

 

1 hour ago, J05u said:

Any updates for Arc driver compatibility?

Probably not as the support is only available on kernel 6.2+ from what I understand.

 

Quote

Linux kernel

version 6.1.46 (CVE-2023-20593)

 

13 hours ago, user12345678 said:

I have a LACP bond that also acts as a VLAN trunk, from there I have several interfaces defined for various VLANs.

 

Disabling bridging will change docker to use the bonded interface, including the VLAN networks.

 

This is my docker set up

 

# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
b773f11c6dcc   bond0     macvlan   local
a9315eb8f702   bond0.3   macvlan   local
5d489327c46b   bond0.4   macvlan   local
d69bccba5929   bond0.5   macvlan   local
a7b83120a899   bond0.6   macvlan   local

 

10 hours ago, Sascha75 said:

My server has 3 NIC's: eth0, eth2, eth3

eth2 and eth3 are down, no IP assignment in the network settings

 

That should work properly (I have 4 NICs), likely a configuration issue. Need to see your diagnostics.

 

2 hours ago, sonic6 said:

The Docker Area in Dashboard is very slow with 6.12.4RC18 .

 

How many containers do you have?

My main server has 30 containers and display is instantaneous on the dashboard.

There are no code changes for the dashboard that would explain a different behavior.

 

6 minutes ago, bonienl said:

How many containers do you have?

41 Containers are running.
I did't change the count on containers in the last weeks.

Is the driver for 2.5Gb Asix usb-network adapter included in this release?

13 hours ago, nraygun said:

And @snowy00, can you confirm you didn’t do anything special (outside of normal upgrade prep) when you went from 6.11.5 to this 6.12.4?

 

Yes, I can confirm it is not necessary do do something special.  

 

My procedure was:

- Stop VM and Docker

- Install Update 

- Change the network settings 

  Settings -> Network Settings -> eth0 -> Enable Bridging = No

  Settings -> Docker -> Host access to custom networks = Enabled

- Start VM and Docker 

- No additional modifications needed 

10 hours ago, bonienl said:

There are no code changes for the dashboard that would explain a different behavior.

 

22 Dockers here and like @sonic6 mentioned, there is definately a changed behaviour since 6.12.4 rc13

 

no changes here besides network setup due macvlan changes, same dockers, same vm's, same plugins, same hardware.

 

turned off bridging

changed docker's to eth0

changed vm's to vhost

 

nothing to worry about as its only cosmetic, but its been more or less instant here and now we have the delay, just to confirm @sonic6 post.

so it was that error i pointed out months ago lol, lets hope it fixes the crashes.

Edited August 23, 2023 by nuhll

I have only noticed it takes longer to check for updates maybe. GUI fast.

 

Whats the

Aug 23 19:07:55 Server monitor: Stop running nchan processes
Aug 23 19:37:28 Server monitor: Stop running nchan processes
Aug 23 20:29:32 Server monitor: Stop running nchan processes

in the logs?

Edited August 24, 2023 by Niklas

11 hours ago, bonienl said:

 

That should work properly (I have 4 NICs), likely a configuration issue. Need to see your diagnostics.

 

maybe that came across wrong, I was simply stating my current set up. I have manually disabled the other 2 NICs.

 

the main issue is that the custom network for eth0 was not available for selection in docker until I added custom network for eth2. I will try to add some screenshots later.

23 hours ago, ljm42 said:

 

Thanks for testing, I've not seen that.

 

On Settings -> Docker, get back to where only there is only a custom network on eth0. If you see the option for macvlan/ipvlan (you may not, depending on other settings), be sure it is set to macvlan. Then take a screenshot of the page.

 

Please take a screenshot of Settings -> Network -> eth0. "Enable bridging" should be no.

 

Then start the array

 

Go to one of your Docker containers and take a screenshot of the "Network Type" options. I would expect to see "Custom: eth0" as an option, ideally selected by default.

 

Then post all of the screenshots and the full diagnostics.zip (from Tools -> Diagnostics)

 

Thanks!

 

I 've tried to reproduce the missing eth0 in docker networks by reverting all settings and repeating them, but was not able to do so. maybe I did no follow the correct order the first time. now my docker on br0 was automatically switched to eth0, as it is described in the instructions.

 

 

First of all, great work! I did as instructed and macvlan works well so far.  Question:

 

I have 3 NICs, eth0 and eth1/eth2, I disabled bridging on eth0, eth1/eth2 is using bonded LACP, with a few VLANs that docker is using. Is it recommended that I disable bridging on ALL interfaces and only use bonding? current Docker network below:

 

root@Unraid:~# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
410ede2fc44b   br1       macvlan   local
8ef814bdd249   br1.10    macvlan   local
24c58ff2a324   br1.15    macvlan   local
18d59eef887b   br1.20    macvlan   local
a65a073f4cd7   bridge    bridge    local
8002478340ab  eth0      macvlan   local
f6e5f48f1e23     host      host      local
5882761c0802  none      null      local

So far its been looking very good. 👍

The Webterminal does work again on mobile (android 13, chrome) but clicking the syslog shortcut still breaks everything.
And while im at the syslog, this is certainly new in .12.4 



this keeps on going for a while. seems to have started after the 24h dc.

4 hours ago, Jclendineng said:

Is it recommended that I disable bridging on ALL interfaces and only use bonding?

 

I recommend to disable bridging and use bond1 instead. We have seen that the new macvtap network gives much better performance than bridging. Though your current set up should work without issues.

 

1 hour ago, Mainfrezzer said:

So far its been looking very good. 👍

The Webterminal does work again on mobile (android 13, chrome) but clicking the syslog shortcut still breaks everything.
And while im at the syslog, this is certainly new in .12.4 



this keeps on going for a while. seems to have started after the 24h dc.

 

i think this is because of the changing ipv6 prefix. fe80 prefixes changes in germany after DC's
so this isn't usable for a static route?

@bonienl can you take a look into that?

56 minutes ago, sonic6 said:

can you take a look into that?

 

Thanks, I made a change to address this.

 

1 hour ago, sonic6 said:

 

i think this is because of the changing ipv6 prefix. fe80 prefixes changes in germany after DC's
so this isn't usable for a static route?

@bonienl can you take a look into that?

That was spot on. The GUA prefix changed. Did notice that wireguard didn't use ipv6 anymore. the eth0 changed correctly but the vhost still used the old ipv6 address, which I reckon is being used.

Okay, throwing this up here because I'm missing something, a bit of a n00b, and maybe just slow and stupid.

 

I had previously implemented ipvlan in Docker. Then I added a NIC (eth1) and implemented the "two-nic solution" to move back to macvlan. Seemed fine.

 

I updated to 6.12.4-rc18 and made what I thought were the recommended changes. I ended up redefining some of the networking for Docker, as this sort of broke all my previous br1 bridges. No worries, really.

 

But, I seem to have Docker on eth0 custom network now. Can I move it to eth1 and if so, how? What am I missing?

 

Here's my setup...

 

 

*note I tried to add routhing for eth1 here but it didn't save.

 

On 8/23/2023 at 1:39 AM, ChatNoir said:

Probably not as the [Intel Arc driver] support is only available on kernel 6.2+ from what I understand.

 

 

That's correct, and the number of moving parts between the Linux 6.1, 6.2, 6.3 kernels, ZFS support, and Arc drivers in the last 9 months has made it very hard to make everybody happy here, I'm sure. I have a A380 installed waiting to add to my container for transcoding on Plex; however the host OS must support it first, which means 6.2 or later. 6.2 isn't LTS (AFAIK there woin't be any more 6.2 kernels?), 6.3 is still in active development and support, so that's the path forward... however OpenZFS only added 6.3 support two months ago. So for unRaid devs and release managers, it's probably a choice between the wide number of use cases and number of users of ZFS versus the very few who have Arc cards as far as deciding what kernel to use; moving to a new kernel requires a ton of regression, I'm sure.

1 hour ago, The_Holocron said:

But, I seem to have Docker on eth0 custom network now. Can I move it to eth1 and if so, how? What am I missing?

 

If you really want to do it, you should disable bridging on eth1 (screenshot 2) and move the custom network from eth0 to eth1 (screenshot 4)

 

But what value do you see in doing this? With the changes in this release, there is no longer a benefit to segregating Docker to its own network, I think you'd be better off keeping things simple and not using eth1

Just now, ljm42 said:

 

But what value do you see in doing this? With the changes in this release, there is no longer a benefit to segregating Docker to its own network, I think you'd be better off keeping things simple and not using eth1

Fair points. I guess I'm trying to figure out what to do with eth1 now...

We've got a new RC with some nice fixes for the weekend 

 

Never had issues with the "original" br0 macvlan, but looking at the technical details: The new macvtap method seems nice and could be the new default, if I understand things correctly. Even if the kernel bug gets addressed, the macvtap on ethX seems a better default. Correct me if misunderstood something.