[Docker - Save/Save and Run]

While modifying docker containers I'm missing a simple function that would allow me to only save my settings and not start the container.

Today when you hit apply the settings are saved and if the container is stopped it will be automatically started which means if you don't want it to you gotta stop it directly after.

 

A simple button, [Save] , [Save and Run] would solve this.

[VM Backup Plugin]

I'm trying to set a custom cron entry but the plugin wont accept my syntax. Why?

 

What I'm using: 0 9 8-14 * Wed

https://crontab.guru/#0_9_8-14_*_Wed

 

[[Support] atunnecliffe - Splunk]

I tried just that and it seems to be working better now. 

 

Thank you.

[[Support] atunnecliffe - Splunk]

This image doesn't seem to be working fully.

 

If you change or Add another Path, Port, Variable, Label or Device or set an IP for the container the whole image gets reset back to factory settings.

[Parity Check and Mover Running Concurrently]

2 minutes ago, johnnie.black said:

 

Parity in unRAID is always updated in real-time.

 

 

Okey so this is why it's reading and writing at the same time. This is kinda bad for performance, hence that's why we use cache drives i guess.

Is there a way to pause the parity check or temporary disable it?

 

[Parity Check and Mover Running Concurrently]

I had the similar experience just now...

 

I copied about 200GB to a share with cache enabled (set to Yes) and when i manually invoked the mover it seems like the copy and the parity are running at the same time because both the data disk and the parity disk reads and writes simultaneously.

I though that unRAID would fist move the data from the cache drive to the data disk then run the parity check. Or does it do both at the same time?

 

Is this normal?