Alexstrasza

Sorry, I forgot all about this. I've made one now:

A way to set the docker stop timeout (normally specified with the -t paramater in the `docker stop` command), per container rather than globally. Use case: Containers which require extra time to stop, in order to save databases and other shutdown tasks (for example, the Storj container), but without increasing system stop time in the event of a misbehaving different container. In addition, this should apply to the "stop" command in the GUI, which I'm unsure if currently obeys the system default. See discussion thread:

There are several feature requests in the feature request forum which are now implemented. Please can we either tag them the same way bug reports work, or perhaps move them to a "Added" subcategory so any feature requests active have not yet been assessed?

At the moment, if you are using a third-party registry (aka, not Docker hub), images that use it have their update status listed as "not available". I think this is just a matter of telling the updater logic to look at the registry the image is from, not "just always try Docker Hub".

Final update: The server has not crashed again, so I can comfortably say that the problem was the overclocked RAM. Thank you everyone for your help!

Update: The server crashed again. I have now reset the RAM overclock so it's running at stock speeds. The panic does always appear to be in some kind of TCP stack, so that might be relevant if it crashes again.

Will do, thanks!

I've enabled "Typical current idle" and will report back if that resolves the panic.

Further information that may be relevant: The server has a 10GBe NIC The server is running a Ryzen 3700X The motherboard is a X470D4U by AsRock Rack I've attached the most recent diagnostics from after the reboot. sector5-diagnostics-20200621-1422.zip

Hi all, The past week or so I've been getting kernel panics on my server. This has definitely been happening on the most recent betas (6.9.0-beta1 and beta22) and may have been happening on the stable release as well. Unfortunately as the kernel panics, there are no logs of what was happening before or what went wrong, attached is the only screenshot I've been able to pull from the console screen. Any suggestions would be much appreciated.

Please can you link me to that pull request? If possible, it would probably make more sense to request they review it again (considering you've already done the work).

Exact same problem with the exact same use-case as @L0rdRaiden. Did anyone find a solution to this? Otherwise I might propose this a a feature request.

No, I don't get any errors at all, yet the drive images don't appear unless I perform that "reset image" shuffle. Scanning Hardware 19:31:49 Spinning up hard drives 19:31:49 Scanning system storage 19:31:50 Scanning USB Bus 19:31:56 Scanning hard drives 19:31:57 Scanning storage controllers 19:31:57 Scanning USB hubs & devices 19:31:57 Scanning motherboard information 19:31:57 Fetching known drive vendors from the HDDB 19:31:58 Found controller SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] 19:31:58 Found drive Seagate ST10000DM0004 Rev: DN01 Serial: / (sdb) 19:31:58 Found drive Western Digital WD80EZAZ Rev: 83.H0A83 Serial: / (sdc) 19:31:58 Found drive Western Digital WD60EFRX Rev: 82.00A82 Serial: / (sdd) 19:31:58 Found drive Western Digital WD80EMAZ Rev: 81.00A81 Serial: / (sde) 19:31:58 Found drive Western Digital WD80EMAZ Rev: 81.00A81 Serial: / (sdf) 19:31:58 Found controller P1 NVMe PCIe SSD 19:31:58 Found drive CT1000P1SSD8 Rev: P3CR013 Serial: / (nvme0n1) 19:31:58 Found controller Matisse USB 3.0 Host Controller 19:31:58 Found drive SanDisk' Cruzer Fit Rev: 0 Serial: / (sda) 19:31:58 Found controller P1 NVMe PCIe SSD 19:31:58 Found drive CT1000P1SSD8 Rev: P3CR013 Serial: / (nvme1n1) 19:31:58 Fetching drive images 19:31:58 Fetching Drive Platter Information 19:31:59 Checking Hard Drive Database for drives 19:31:59 Configuration saved

For some reason drive images don't seem to be downloading for me, even though I've checked the database and my drives are present. If I add a custom image, and then click "reset image", they show up then.