Disk3 is just CRC. You can acknowledge that by clicking on the warning on the Dashboard and it will warn again if it increases.
Unfortunately, disk1 is more serious:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
187 Reported_Uncorrect -O--CK 100 001 000 - 23516
I would replace that ASAP. Hopefully you can build parity so you can do a replacement.
I see you have a 1TB unassigned, it also has a warning but that is just a single Reported Uncorrect. But you might as well skip using that one as parity if you intend to replace your disks with 2TB soon. Parity must be at least as large as the largest single data disk, so you would have to build 2TB parity before you could replace any data disks.
You might consider using that 1TB as disk1 instead of that bad one you already have in that slot. That would require working through some things to make that replacement since you don't currently have parity.
Also see you have 120GB SSD. That is too small for much use caching user share writes, but should be fine if you only use it for dockers and VMs.
And as I already mentioned, enabling dockers before installing cache wasn't the best idea. That will also require working through some things to get your dockers on cache where they belong.
Personally, I would skip over 2TB and build a server with at least 4TB disks, using fewer disks if you can't afford it.