4.10.2 - ContentDelivery container not starting

In the 4.10.2 update, there may be cases where the ContentDelivery container fails to start. 

Symptom: 
ContentDelivery container is not healthy in the Container Status page. There is an error message either in the ContentDelivery{yyyymmdd}.log file in /loginvsi/logs or in the container log available in portainer. 
Note: This container failing to start may cause other containers to fail to start as well. 

Confirmation:

To confirm the fix below is relevant to this instance of the container not starting, run the following commands and verify the output may be similar:

ls -la /loginvsi/content/zip/launcher_* 

is similar to:

-r-xrwxr-x 1 admin loginenterprise 33267795 Dec 15 17:10 /loginvsi/content/zip/launcher_linux_x64.tar.bz2
-r-xrwxr-x 1 admin loginenterprise 70635369 Dec 15 17:16 /loginvsi/content/zip/launcher_win10_x64.zip

and 

ls -la /loginvsi/content/zip

is similar to:

drwxrwxr-x 4 admin loginenterprise 4096 Nov 9 12:10 .
drwxr-xr-x 10 admin admin 4096 Nov 29 16:23 ..
-rw-rw-r-- 1 admin loginenterprise 9697650 Dec 15 17:16 engine.zip
-r-xrwxr-x 1 admin loginenterprise 106112 Dec 15 17:10 eux2021.zip
-rw-rw-r-- 1 admin loginenterprise 4161558 Dec 15 17:16 eventlogger_x64.zip
drwxrwxr-x 2 admin loginenterprise 4096 Nov 9 12:10 igel
-r-xrwxr-x 1 admin loginenterprise 33267795 Dec 15 17:10 launcher_linux_x64.tar.bz2
-r-xrwxr-x 1 admin loginenterprise 70635369 Dec 15 17:16 launcher_win10_x64.zip
-rw-rw-r-- 1 admin loginenterprise 185632 Dec 15 17:10 logon.zip
-rw-rw-r-- 1 admin loginenterprise 164513916 Dec 15 17:10 ScriptEditor.zip
-rw-rw-r-- 1 admin loginenterprise 86168363 Dec 15 17:10 ScriptingToolSet.zip
drwxrwxr-x 2 admin loginenterprise 4096 Nov 9 12:04 secured

Resolution:

Log into the management console and open the bash shell from the troubleshooting menu. Execute the following command:

find /loginvsi/content/zip/ -type f -print0 | xargs -0 chmod 664

Allow a few minutes to pass before returning to the web appliance Container Status page to confirm all containers are now healthy. Containers should restart on their own. 

Rerunning the command below should show the following permissions:

ls -la /loginvsi/content/zip

drwxrwxr-x 4 admin loginenterprise 4096 Nov 9 12:10 .
drwxr-xr-x 10 admin admin 4096 Nov 29 16:23 ..
-rw-rw-r-- 1 admin loginenterprise 9697650 Dec 15 17:16 engine.zip
-rw-rw-r-- 1 admin loginenterprise 106112 Dec 15 17:10 eux2021.zip
-rw-rw-r-- 1 admin loginenterprise 4161558 Dec 15 17:16 eventlogger_x64.zip
drwxrwxr-x 2 admin loginenterprise 4096 Nov 9 12:10 igel
-rw-rw-r-- 1 admin loginenterprise 33267795 Dec 15 17:10 launcher_linux_x64.tar.bz2
-rw-rw-r-- 1 admin loginenterprise 70635369 Dec 15 17:16 launcher_win10_x64.zip
-rw-rw-r-- 1 admin loginenterprise 185632 Dec 15 17:10 logon.zip
-rw-rw-r-- 1 admin loginenterprise 164513916 Dec 15 17:10 ScriptEditor.zip
-rw-rw-r-- 1 admin loginenterprise 86168363 Dec 15 17:10 ScriptingToolSet.zip
drwxrwxr-x 2 admin loginenterprise 4096 Nov 9 12:04 secured