Skip to content

Issue running selenium/standalone-chrome on arm64 #13

@tonistiigi

Description

@tonistiigi

Running Docker Desktop on Apple M1. Reported on dev preview feedback

i just tried some containers, most of them work fine for me. one that's though misbehaving is the selenium one...
it's run like described in this repo: https://github.com/SeleniumHQ/docker-selenium via docker run -d -p 4444:4444 -p 5900:5900 -v /dev/shm:/dev/shm selenium/standalone-chrome:4.0.0-beta-1-prerelease-20201208 . connecting with a vnc viewer works well, when trying to launch the chrome application (right click on desktop -> applications -> network -> web browsing -> google chrome) there's nothing happening though.
log file in /var/log/supervisor/xvfb-stdout.log reports this only. just wanted to give you a shout, don't know anything specific about that image but i'd imagine it's used by some people for selenium testing.

Trace/breakpoint trap
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[387:387:1212/163414.315133:ERROR:nacl_fork_delegate_linux.cc(329)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[360:395:1212/163414.401966:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38)
[360:399:1212/163414.827603:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
qemu: unknown option 'type=utility'
[360:413:1212/163415.286343:ERROR:bus.cc(393)] Failed to connect to the bus: Address does not contain a colon
[360:413:1212/163415.286761:ERROR:bus.cc(393)] Failed to connect to the bus: Address does not contain a colon
[360:413:1212/163415.493547:ERROR:bus.cc(393)] Failed to connect to the bus: Address does not contain a colon
[360:413:1212/163415.494039:ERROR:bus.cc(393)] Failed to connect to the bus: Address does not contain a colon
[360:397:1212/163415.748544:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped

Possibly related: https://bugs.launchpad.net/qemu/+bug/1890545

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions