(04-20-2020, 03:57 PM)Luke Wrote:(04-20-2020, 12:41 PM)hthiemann Wrote: Currently hw accelaration is still a missing feature, but I thought I could share my current version with you - maybe someone has an idea how to fix this
Please find my code and a detailled description here: https://github.com/HenningThiemann/docker-chromium-armhf
Essentially, you need to
- enable XHost Forwarding to allow the docker container to spin up a new XFrame Window (xhost +local:docker)
- create a new docker volume to persist your chromium settings (docker volume create chromium_home)
- spin up the container with the following command
docker run --rm --privileged \ -e DISPLAY=unix$DISPLAY \ -v chromium_home:/home \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -v /dev:/dev -v /run:/run \ -v /etc/machine-id:/etc/machine-id \ --ipc=host \ hthiemann/docker-chromium-armhf
- Tested with netflix and spotify, both working
Awesome work, have you set the required flags? - for starters un-blacklist the GPU?. Then see if you get acceleration (easily checked under chrome://gpu).
For reference, in chrome://flags look for:
Code:#ignore-gpu-blacklist
#enable-gpu-rasterization
I've copied all flags from the mrfixit debian repo and see they are available in chromium.
I have added the "mesa-utils" and "mesa-utils-extra" packages inside the container, in theory "HW acceleration" should be available now (as displayed inside chromium) - but I doubt it really is as the performance is about on the same level as before.