Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

depending of what you mean by friction with containers, there may be different solutins. for example, as a temporary solution on Docker when you don't want/have time to support both arm and x86, you can do something like this: FROM --platform=linux/x86_64 ubuntu:23.04

i haven't found any issues with it that i could not get over in the past 2+ years of m1. most of the containers are available on both architectures anyway. the performance improvement was totally worth it, i won't even talk about the heating issue with intel.



> i haven't found any issues with it that i could not get over in the past 2+ years of m1.

I'm currently running a Journal of Open Source Software x86 container on aarch64 and it's terribly slow. Takes 12GB of RAM and 3 minutes to build a LaTeX document, see https://github.com/openjournals/inara/issues/30. Any tips?


Building a single-page LaTeX document as a PDF can be done in less than 0.3s when the environment is set up correctly. I don't know anything about this particular container.


> I'm currently running a Journal of Open Source Software x86 container on aarch64 and it's terribly slow

There's your issue. Use an aarch64 image.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: