tensorflow/latest image crashes with qemu core dump as soon as Tensorflow is loaded on M1

[jantuitman]

• [x ] I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: I cannot find a button for it in your UI.

STEPS TO REPRODUCE:

MacOS: 11.0.1, Apple MacBook Pro (13-inch,M1,2020)

docker-compose.yml:

version: "3.4"
services:
  pie:
    image: "tensorflow/tensorflow:latest"
    command: /bin/bash  
    volumes:
      - ./:/home/root/work

next:
docker-compose run pie

inside the docker image, start python, and require Tensorflow:

root@d1e9397ee486:/home/root/work# python
Python 3.6.9 (default, Oct  8 2020, 12:12:24) 
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
2021-02-12 21:25:20.268211: F tensorflow/core/lib/monitoring/sampler.cc:42] Check failed: bucket_limits_[i] > bucket_limits_[i - 1] (4.17216e-152 vs. 10)
qemu: uncaught target signal 6 (Aborted) - core dumped

expected behavior:

no crash.

actual behavior:

see above.

[stephen-turner]

Thank you for the report. This is a qemu bug, which is the upstream component we use for running Intel containers on M1 chips, and is not something we control. We would recommend

1. encouraging the container author to supply an arm64 or multi-arch image, not just an Intel one
2. if that fails, report a bug to https://www.qemu.org/contribute/report-a-bug/

[gmondo]

I have a similar problem with a slightly different environment. Could you confirm it is the same problem?
I am using qemu on an Intel i5-8365U with the following options -machine q35,kernel-irqchip=split,accel=kvm and I get:

user@ubuntu:~$ python3
Python 3.7.10 (default, Feb 20 2021, 21:17:23)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
2021-02-23 22:31:31.380280: F tensorflow/core/lib/monitoring/sampler.cc:42] Check failed: bucket_limits_[i] > bucket_limits_[i - 1] (4.17216e-152 vs. 10)
Aborted

Regards

[scchess]

I got the problem too.

[kd610]

I also got the same issue now...

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked