Topics created by LadislavBohm

thanks for the details!

i was able to see in logs the error that you were mentioning, however i did not found anything special about it that could help to discover the reason of the issue. my advice, if you ever see this error again, would be that you let the original template as it is and let us know inmediatly so we have something to debug, in that case you can continue with your reports by cloning the template and use that clone instead for your final reports.

thanks for the information, the full image just does npm install jsreport-mongodb-store so there is a chance that when you build the image you get more recent versions of mongodb store (in theory this should not happen because the way how docker build cache should work, you should always get 1.1.0). for example i just ran a container with 2.0.0-full and latest-full and i got 1.1.0 version of jsreport-mongodb-store in both cases. probably it is weird npm/docker cache issue, in future we will try to find a way to have more static version of extensions per release, so we don't have these random results when installing packages.