So i've been messing with this for a couple of weeks but I can't get it fully solved. 
I've got an empty docker and its job is to download and update an game with steamCMD and then extract files automatically. It often ends in an error, but running it again makes it work flawless. 

 

The docker output.  As far I can find error 1 is an issue to write to disk. It writes straight into a volume that's 2x nvme in parity. I enabled turbo write which helped but still its giving me issue, odd enough doing it again make it work sucessfully. 

WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/home/workspaces/Steam/logs/stderr.txt'
Logging directory: '/home/workspaces/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logo
Steam Console Client (c) Valve Corporation - version 1741737873
-- type 'quit' to exit --
Loading Steam API...IPC function call IClientUtils::GetConnectedUniverse took too long: 50 msec
IPC function call IClientUtils::GetIPCountry took too long: 50 msec
IPC function call IClientUtils::GetServerRealTime took too long: 49 msec
IPC function call IClientUtils::SetAppIDForCurrentPipe took too long: 49 msec
IPC function call IClientUtils::GetAppID took too long: 50 msec
IPC function call IClientUtils::SetLauncherType took too long: 50 msec
OK
IPC function call IClientUtils::SetSpew took too long: 44 msec
Logging in using username/password.
Logging in user 'fabricenl' [U:1:81842769] to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
IPC function call IClientAppManager::GetUpdateInfo took too long: 42 msec
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
 Update state (0x5) verifying install, progress: 1.96 (709186937 / 36201592000)
 Update state (0x5) verifying install, progress: 4.91 (1777371337 / 36201592000)
 Update state (0x5) verifying install, progress: 7.68 (2780100927 / 36201592000)
 Update state (0x5) verifying install, progress: 10.64 (3852093482 / 36201592000)
 Update state (0x5) verifying install, progress: 13.55 (4904131682 / 36201592000)
 Update state (0x5) verifying install, progress: 16.50 (5972107858 / 36201592000)
 Update state (0x5) verifying install, progress: 19.45 (7041782738 / 36201592000)
 Update state (0x5) verifying install, progress: 22.41 (8113453570 / 36201592000)
 Update state (0x5) verifying install, progress: 25.31 (9162750553 / 36201592000)
 Update state (0x5) verifying install, progress: 28.14 (10185840793 / 36201592000)
 Update state (0x5) verifying install, progress: 30.92 (11193433689 / 36201592000)
 Update state (0x5) verifying install, progress: 33.82 (12243110633 / 36201592000)
 Update state (0x5) verifying install, progress: 36.53 (13223493289 / 36201592000)
 Update state (0x5) verifying install, progress: 39.31 (14231779545 / 36201592000)
 Update state (0x5) verifying install, progress: 42.16 (15262142457 / 36201592000)
 Update state (0x5) verifying install, progress: 45.05 (16310543233 / 36201592000)
 Update state (0x5) verifying install, progress: 47.91 (17345602112 / 36201592000)
 Update state (0x5) verifying install, progress: 50.86 (18413142027 / 36201592000)
 Update state (0x5) verifying install, progress: 53.79 (19471319003 / 36201592000)
 Update state (0x5) verifying install, progress: 56.70 (20527687454 / 36201592000)
 Update state (0x5) verifying install, progress: 59.56 (21561510813 / 36201592000)
 Update state (0x5) verifying install, progress: 62.47 (22615794269 / 36201592000)
 Update state (0x5) verifying install, progress: 65.08 (23561111415 / 36201592000)
 Update state (0x5) verifying install, progress: 67.66 (24494259987 / 36201592000)
 Update state (0x5) verifying install, progress: 70.48 (25514394851 / 36201592000)
 Update state (0x5) verifying install, progress: 73.32 (26543438017 / 36201592000)
 Update state (0x5) verifying install, progress: 76.24 (27599040461 / 36201592000)
 Update state (0x5) verifying install, progress: 79.20 (28672656449 / 36201592000)
 Update state (0x5) verifying install, progress: 82.00 (29683596857 / 36201592000)
 Update state (0x5) verifying install, progress: 84.75 (30680628807 / 36201592000)
 Update state (0x5) verifying install, progress: 87.57 (31702993729 / 36201592000)
 Update state (0x5) verifying install, progress: 90.41 (32730071591 / 36201592000)
 Update state (0x5) verifying install, progress: 93.04 (33681074900 / 36201592000)
 Update state (0x5) verifying install, progress: 95.70 (34643766679 / 36201592000)
 Update state (0x5) verifying install, progress: 98.35 (35604992202 / 36201592000)
Error! App '227300' state is 0x10C after update job.

 

vtlog-diagnostics-20250316-1608.zip

Not seeing any issues with Docker in general, is the problem with just that container?

13 hours ago, TheFabby said:

It writes straight into a volume that's 2x nvme in parity. I enabled turbo write which helped but still its giving me issue, odd enough doing it again make it work sucessfully. 

Are using the nvmes in the array or in a pool?

Are you using the fuse path as bind mount or the "real" path (.ie something like /mnt/cache, /mnt/disk1)
 

10 hours ago, Mainfrezzer said:

Are using the nvmes in the array or in a pool?

Are you using the fuse path as bind mount or the "real" path (.ie something like /mnt/cache, /mnt/disk1)
 

Surely il sounds like an idiot but i've no clue how to see the difference of pool or array but my MAIN says array. 

As for the volume path its
/home/workspaces in the container to /mnt/user/vscode/vscode2/workspaces

We run a custom docker image with
OpenLiteSpeed (Webserver)
Redis
OpenVSCode Server

So my thought was inside vscode since it has a terminal to use steamCMD to download two games so I can extract the data more automated as its all manual work now. However i've had more issues in past with dockers showing in logs they have issues writing, especially if its larger files
 

3 hours ago, TheFabby said:

Surely il sounds like an idiot but i've no clue how to see the difference of pool or array but my MAIN says array. 

As for the volume path its
/home/workspaces in the container to /mnt/user/vscode/vscode2/workspaces

We run a custom docker image with
OpenLiteSpeed (Webserver)
Redis
OpenVSCode Server

So my thought was inside vscode since it has a terminal to use steamCMD to download two games so I can extract the data more automated as its all manual work now. However i've had more issues in past with dockers showing in logs they have issues writing, especially if its larger files
 

That setup would makes more sense as a pool of a raid 1 mirror of btrfs or even zfs. (https://docs.unraid.net/unraid-os/manual/storage-management/#why-use-a-pool)

granted, the documentation is a tat out of date. Especially since you dont need to have an array anymore at all


Regardless, try changing the mapping from /mnt/user/vscode (or whatever container mapping you have) to /mnt/disk1/vscode and see if it still happens.

Alright, I tried but still same issue. "Regardless, try changing the mapping from /mnt/user/vscode (or whatever container mapping you have) to /mnt/disk1/vscode and see if it still happens." 

I will have a look in upcoming weeks to find a day to move everything off the drives and make it a pool instead. Thank you so far ❤️