Topics created by lennykey

Please email me the workspace zip and config file and describe the steps to reproduce the issue. Thank you.

Maybe you would have better results with mapping normal file system disk and using the default fs store instead of the s3.

Hi @jan_blaha ,

I tried to find a way to solve or overcome my issue and maybe this is interesting to share with others

FROM jsreport/jsreport:2.11.0 COPY jsreport.config.json jsreport.config.json RUN mkdir /app/.npm-global RUN npm install \ jsreport-fs-store-aws-s3-persistence@1.4.1 \ jsreport-fs-store-aws-sns-sync@1.2.1 \ --cache /app/.npm-global RUN chmod +x /app/run.sh EXPOSE 5488 CMD /app/run.sh

Fist step is to create a npm cache folder where the jsReport user in the Docker file has acces to write

RUN mkdir /app/.npm-global

And in the second step to re-use this folder via npm

RUN npm install \ jsreport-fs-store-aws-s3-persistence@1.4.1 \ jsreport-fs-store-aws-sns-sync@1.2.1 \ --cache /app/.npm-global

I hope this helps some using Kubernetes and creating the image via Kaniko

Hi @jan_blaha ,

to give you further feedback on this topic.

Your provided solution works now for the full and non full version of jsReport in Kubernetes. Thank you very much for this hint:

extensions_fsStoreAwsS3Persistence_bucket

Maybe it is only a Kubernetes issue but

extensions_fs-store-aws-s3-persistence_bucket

only works for the non full version of jsReport. The full jsReport versions are not respecting the environment variable.

Thank your for your hint

Thank you for the update.