[[6.9.2] Docker with multiple connected networks cannot start on reboot / docker daemon restart]

Awesome. Been waiting for this!

 

Also the DHCP vs local thing. many times i've had the issue where it would simply assign a duplicate network address because it couldn't communicate over the vlan's yet.... I can finally make it dynamic again!

[[6.9.2] Docker with multiple connected networks cannot start on reboot / docker daemon restart]

so . . . since i am still having the issue, i figured i would come here.

Now, the thing is . . . i understand what you're saying and what i need to do.

However . . . how do i get to the file?

 

Perhaps this could be a userscript?

[Unraid OS version 6.10.0-rc3 available]

25 minutes ago, ChatNoir said:

The solution is to fix the hardware issue, not removing the tool detecting the issue.

RAM erroring is not OK. An alert to the user is the expected result, whether ECC can manage or not.

perhaps, but still i want to have the ability to ignore things. like i had before with nerdpack.

Or simply turn it on when i actually want it on.

 

[Unraid OS version 6.10.0-rc3 available]

Really only 1 question . . . how do i turn off the now build-in mcelog? i have 1 memory module that is throwing errors like no tommorow, (just an ECC correction message) and the logs are filling up with this.

[[6.9.2] Hypervisor memory leak [Solved with 6.10.0 RC2]]

Good day all,

 

Since upodating to 6.10.0 RC2 and restarting everything. The issue with memory leaking seems to have completely resolved. I am nolonger able to reproduce the memory leak issues i have experienced in both windows and ubuntu VM's.

 

Hope this makes it to final stable build!

[[6.9.2] Hypervisor memory leak [Solved with 6.10.0 RC2]]

Gday all,

 

So i upgraded to 6.10.0 RC2 about 11 days ago.

Since then, the memory leak is less (for now).

Continuing to monitor the state.