Running Docker image with Matlab on a Mac

Hi,
We have been trying to dockerize some of our Matlab workflows, which has worked perfectly fine. However, we are running into problems when we try to run the same docker image on a Mac computer. Upon launching matlab, we get the following error:
% root@0488926e7766:/workdir# matlab
% MATLAB is selecting SOFTWARE OPENGL rendering.
% Fatal Internal Error: std::exception: uint64_t foundation::core::system::linux::x86_64::getMaximumProcessorFrequencyImpl(): Numerical result out of range
Poking around the output of lspcu, presumably the problem is related to the CPU MHz value, which is reported as being 0.000:
root@d4b5480eab78:/workdir# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 61
Model name: Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
Stepping: 4
CPU MHz: 0.000
BogoMIPS: 6979.58
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 4096K
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht pbe syscall nx pdpe1gb lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid pni pclmulqdq dtes64 ds_cpl ssse3 sdbg fma cx16 xtpr pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch pti fsgsbase bmi1 avx2 bmi2 erms xsaveopt arat
The problem has been replicated on systems running High Sierra and Mojave.
Is this a known issue and/or is there a workaround?
Thanks!

5 Comments

Having the same issue. This has started to happen when I updated the docker engine.
The problem is CPU MHz: 0.000
One way would be to emulate the CPU MHz from the host and emulate /proc/cpuinfo with an appropriate number.
The proper way would be for Mathworks to fix this.
@Evi Vanoost How do we emulate /proc/cpuinfo?
I think this may be relevant:
https://github.com/docker/for-mac/issues/6047

Sign in to comment.

Answers (1)

This problem resolved itself by compiling my Matlab code with a newer version of Matlab (2022b instead of 2017b)

Categories

Products

Release

R2019b

Tags

Asked:

on 8 Jun 2020

Answered:

on 1 Dec 2023

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!