Does not work with Apple Silicon (M1) using Docker for Desktop Preview



  • Im using docker desktop in my Apple Macbook Pro with M1 aka Apple Silicon, and uses the docker image jsreport/jsreport:2.11.0-full and it does not work
    0_1613664197639_upload-077520d3-9a91-4965-8633-a186ecc15195

    Here is the error that I got from when ever i used Chrome PDF as recipe. Take note that I'm using the sample data so there should be no problem with the template itself.
    0_1613664392865_upload-0b5a07f2-36ec-406b-85ec-d6e6523a31cb

    After a quick Google, I saw this https://github.com/puppeteer/puppeteer/issues/6258, and https://github.com/puppeteer/puppeteer/issues/6622.


  • administrators

    hi @Rommel-Manalo, as you know the Apple M1 is brand new, so it is expected that software will take some time to support it without problems.

    is this just a problem with docker? i mean, are you able to run jsreport as normal node.js application (no-docker)? the problem here is more about the ability for docker/chrome to be able to run normally on M1, we haven't tried yet an execution on a M1 machine, we probably can not do anything about the docker/chrome M1 support, but we will keep an eye on the issues of those repositories.



  • I can confirm that it just a docker & m1 & chrome-pdf/puppeteer (combination problem only). I have docker & m1 & mongo working fine. BTW running it on normal jsreport code (nodejs) & M1 works fine with me.

    Let see how the docker/chrome M1 progress



  • Hi @Rommel-Manalo, after 1 year I have the same problem... did you solve it?



  • I'm having the same problem.
    PDF report are not working on Apple M1 architecture.
    Does someone have an image for jsreport 2.11 which works on M1

    Alternatively, I would like to know if the version 3 images have the same issue?
    I.e. would upgrading solve this problem?

    Thanks for your consideration,
    Axel


  • administrators

    just to provide some answer here, I mainly work with macOS however with the Intel hardware. considering that 1 year has passed since M1 release, I expect the problems with docker to be less than before, however, this is still just my impression and it is not based on real testing, we don't have YET M1 hardware available to test the images, but this is changing soon (in like 2 or 3 months), I will provide another reply with all my findings when I have the M1 finally on my hands.

    thanks!


Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.