CSS missing after CI deployment / sharing dynamic CSS with multiple instances

Hi,
recently we migrated an Enfold site into our Docker environment where we deploy our wordpress sites using CI/CD tools. The move solved a problem we had with the builtin Layerslider, but now a one came up:

After deployment, the site looks defaced due to missing dynamically generated CSS files. We then have to manually go to the theme option settings page wp-admin/admin.php?page=avia and save the settings (even without changing values) to resolve this.

Our uploads folder is persistent, so the content of uploads/dynamic_avia/… with files like avia-merged-styles-ddf276684ae525538791a02cb0e618c9—687602ac906a5.css survives deployments, but it seems as if after deployment the old dynamic css are not being used so reset/regeneration is necessary.

How can we ensure that the CSS are generated upon deployment, mabye using a WPCLI action to enforce CSS generation? Or can/should we simply delete the wp-content/uploads/dynamic_avia/ folder?

Also, if we run more than one WordPress container (in case of high load) sharing a common uploads directory, will the dynamic file names interfere?

REgards
Ulrich

• This topic was modified 4 hours, 25 minutes ago by onlineprodcontent. Reason: typo fix