You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Be careful, Chrome can output some Warning without affecting the behavior of this image like this one [0709/182256.661108:WARNING:dns_config_service_posix.cc(335)] Failed to read DnsConfig.
To Reproduce
Steps to reproduce the behavior:
Indicate the version of the image using docker image inspect --format='{{index .RepoDigests 0}}' zenika/alpine-chrome
Status: Downloaded newer image for zenika/alpine-chrome:102
[0721/042509.259825:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0721/042509.260105:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0721/042509.264414:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig.
[0721/042509.301728:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is disabled, ANGLE is
[0721/042509.317423:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[0721/042509.384087:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig.
* Connection closed *
What is the expected behavior?
screenshot
What is the actual behavior?
Dead, not working
Logs
Don't know how to check the log.
Versions
Software
Version(s)
How-to
Chromium
102.0.5005.61
docker container run -it --rm --entrypoint "" zenika/alpine-chrome chromium-browser --version
I'm seeing the same issue when attempting to run the following on an M1 Mac:
docker container run -it --platform linux/arm64 --rm --cap-add=SYS_ADMIN zenika/alpine-chrome
[0824/013038.961704:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0824/013038.961771:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0824/013038.962088:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig.
[0824/013038.964579:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[0824/013038.965128:ERROR:gl_factory.cc(128)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none),(gl=egl-angle,angle=swiftshader)].
[0824/013038.968423:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[0824/013038.973087:ERROR:gl_factory.cc(128)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none),(gl=egl-angle,angle=swiftshader)].
[0824/013038.974692:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[0824/013038.999396:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig.
Describe the bug
A clear and concise description of what the bug is.
Be careful, Chrome can output some
Warning
without affecting the behavior of this image like this one[0709/182256.661108:WARNING:dns_config_service_posix.cc(335)] Failed to read DnsConfig.
To Reproduce
Steps to reproduce the behavior:
docker image inspect --format='{{index .RepoDigests 0}}' zenika/alpine-chrome
sudo docker container run -it --rm -v $(pwd):/usr/src/app zenika/alpine-chrome --no-sandbox --screenshot --hide-scrollbars --disable-gpu --cap-add=SYS_ADMIN --hide-scrollbars https://www.baidu.com
What is the expected behavior?
screenshot
What is the actual behavior?
Dead, not working
Logs
Don't know how to check the log.
Versions
docker container run -it --rm --entrypoint "" zenika/alpine-chrome chromium-browser --version
docker image inspect --format='{{index .RepoDigests 0}}' zenika/alpine-chrome
docker version
Additional context
Cpu model :
The text was updated successfully, but these errors were encountered: