Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Chrome under amd64 emulation (M1) results in crashes #5766

Closed
Niek opened this issue Jun 18, 2021 · 4 comments
Closed

Running Chrome under amd64 emulation (M1) results in crashes #5766

Niek opened this issue Jun 18, 2021 · 4 comments

Comments

@Niek
Copy link

Niek commented Jun 18, 2021

Any amd64 container with Chrome crashes on arm64 hosts (M1 architecture). Here is a quick sample:

docker run --rm -p 3000:3000 --platform linux/amd64 -e "PREBOOT_CHROME=true" browserless/chrome

The stderr of Chrome is:

qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[2779:2779:0618/071644.009222:ERROR:nacl_fork_delegate_linux.cc(329)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[2737:2787:0618/071644.207029:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Function not implemented (38)
[0618/071646.632623:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Function not implemented (38)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
[0618/071646.653015:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)
Segmentation fault
[0618/071646.653862:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)
[0618/071646.662575:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)

This qemu issue seems to be related: https://gitlab.com/qemu-project/qemu/-/issues/324

Related issue: #5168
Another related issue: #5321

@Niek
Copy link
Author

Niek commented Jun 18, 2021

The qemu crash can be worked around with by adding --no-zygote. However, Chrome still fails to start because of missing inotify support.

@joubertredrat
Copy link

joubertredrat commented Jun 18, 2021

Same issue here. Since upgraded to last stable version, this issue affected me too.

I'm running this compose below and 2 services is getting this issue, other services in this compose is working fine.

dev@Devs-MacBook-Pro ~/source/opensource/joubertredrat/devbox (master)> make kafka6.1-logs
docker-compose -f kafka/6.1/docker-compose.yml -p devbox logs -f
Attaching to devbox_kafdrop.kafka61.devbox.local_1, devbox_kafka-ui.kafka61.devbox.local_1, devbox_broker3.kafka61.devbox.local_1, devbox_broker2.kafka61.devbox.local_1, devbox_broker1.kafka61.devbox.local_1, devbox_zookeeper.kafka61.devbox.local_1
broker1.kafka61.devbox.local_1    | ===> User
broker1.kafka61.devbox.local_1    | uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
broker1.kafka61.devbox.local_1    | ===> Configuring ...
broker2.kafka61.devbox.local_1    | ===> User
broker2.kafka61.devbox.local_1    | uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
broker2.kafka61.devbox.local_1    | ===> Configuring ...
kafdrop.kafka61.devbox.local_1    |
kafdrop.kafka61.devbox.local_1    | :::    :::     :::     :::::::::: :::::::::  :::::::::   ::::::::  :::::::::        ::::::::
kafdrop.kafka61.devbox.local_1    | :+:   :+:    :+: :+:   :+:        :+:    :+: :+:    :+: :+:    :+: :+:    :+:      :+:    :+:
kafdrop.kafka61.devbox.local_1    | +:+  +:+    +:+   +:+  +:+        +:+    +:+ +:+    +:+ +:+    +:+ +:+    +:+             +:+
kafdrop.kafka61.devbox.local_1    | +#++:++    +#++:++#++: :#::+::#   +#+    +:+ +#++:++#:  +#+    +:+ +#++:++#+           +#++:
kafdrop.kafka61.devbox.local_1    | +#+  +#+   +#+     +#+ +#+        +#+    +#+ +#+    +#+ +#+    +#+ +#+                    +#+
kafdrop.kafka61.devbox.local_1    | #+#   #+#  #+#     #+# #+#        #+#    #+# #+#    #+# #+#    #+# #+#             #+#    #+#
kafdrop.kafka61.devbox.local_1    | ###    ### ###     ### ###        #########  ###    ###  ########  ###              ########
kafdrop.kafka61.devbox.local_1    |
broker3.kafka61.devbox.local_1    | ===> User
broker3.kafka61.devbox.local_1    | uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
broker3.kafka61.devbox.local_1    | ===> Configuring ...
zookeeper.kafka61.devbox.local_1  | ===> User
zookeeper.kafka61.devbox.local_1  | uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
zookeeper.kafka61.devbox.local_1  | ===> Configuring ...
zookeeper.kafka61.devbox.local_1  | ===> Running preflight checks ...
zookeeper.kafka61.devbox.local_1  | ===> Check if /var/lib/zookeeper/data is writable ...
kafka-ui.kafka61.devbox.local_1   | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
zookeeper.kafka61.devbox.local_1  | ===> Check if /var/lib/zookeeper/log is writable ...
kafdrop.kafka61.devbox.local_1    | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
zookeeper.kafka61.devbox.local_1  | ===> Launching ...
zookeeper.kafka61.devbox.local_1  | ===> Launching zookeeper ...
broker1.kafka61.devbox.local_1    | ===> Running preflight checks ...
broker1.kafka61.devbox.local_1    | ===> Check if /var/lib/kafka/data is writable ...

https://github.com/joubertredrat/devbox/blob/master/kafka/6.1/docker-compose.yml
https://hub.docker.com/r/obsidiandynamics/kafdrop
https://hub.docker.com/r/provectuslabs/kafka-ui

Other issue that I don't know if is related is my kubernets doesn't work, does eternal "starting".

My setup:

  • Macbook Pro M1 2020
  • Mac OS Big Sur 11.4
  • docker-compose 1.29.2
  • docker engine: 20.10.7
  • docker desktop 3.4.0
  • qemu 5.2.0
  • I have tried disabling enabled experimental features

@stephen-turner
Copy link
Contributor

Closing as documented. https://docs.docker.com/docker-for-mac/apple-silicon/#known-issues

We don't have control over qemu and it's "best effort" only. We have documented both the occasional crashes and the lack of inotify support.

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jul 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants