It's not a clustering config, but rather a recommendation to increase some automatic internal intervals to ensure better run when multiple servers are writing to the same disk. It will work also without those changes.
Do you mean you reference remote images in <img src='your url'/> and then let the chrome to convert to pdf? In this case, jsreport does not influence how these images are loaded and converted. Everything is done by chrome. There is typically no limit on how many images chrome can convert.
It seems like the fix available in 4.6.0 is only applying to default path of puppeteer.
Is there any way to apply the fix to the chromium path specified in launchOptions of jsreport.config.json
We had only updated the puppeteer in the 4.6.0. Nothing more. The perm problem is fixed in the new chrome installer as far as I've read the issues in chrome/puppeteer repo. You may have to run that icacls command on your own during the app startup.
These are the azure system logs which aren't useful to me. Please share the app logs (stdout/stderr) from the app container.
This can be enabled somewhere in the azure portal...
You use the "render for every page" pdf utils merge option.
This makes jsreport re-rendering the header for every page.
This was an original approach we used many years ago.