search

balena-io-experimental / browser

A drop-in web browser block
102 stars 80 forks source link

Example doesn't work anymore #96

Closed titouanc closed 2 years ago

titouanc commented 2 years ago

Hello,

Since yesterday, this container balenablocks/browser doesn't seem to properly start anymore, even though I have seen it working 2 days ago

Steps to reproduce

  1. Create a new fleet in Balena (x86-64 qemu)
  2. Download and launch a qemu image for the newly created fleet
  3. Use the following docker-compose.yml (copied from the README of this repo): 
    
version: '2'

volumes: settings: # Only required if using PERSISTENT flag (see below)

services:

browser: image: balenablocks/browser privileged: true # required for UDEV to find plugged in peripherals such as a USB mouse network_mode: host ports:

phil-d-wilson commented 2 years ago

Hey @titouanc

Thanks for the repro - I'm pushing the block to a device now, and I'll take a look when I can.

It appears to be failing to connect to the debug port, which is odd. I suspect it will be something changed in Chromium.

titouanc commented 2 years ago

Thank you for the very fast reply @phil-d-wilson ! In the meantime, is there a way I could pin this container to a previously working version ?

phil-d-wilson commented 2 years ago

Strangely @titouanc I cannot recreate the problem at all - the block is working fine for me on a PiZero2, Pi3 and Pi4.

titouanc commented 2 years ago

@phil-d-wilson I just tested on a Raspberry Pi 3 (64b) and it does indeed work correctly. Could it be a problem with the x86-64 image only ?

When looking at https://registry.hub.docker.com/v2/repositories/balenablocks/browser/tags, I see that the x86-64 image has been updated yesterday, which matches the moment I started having problems.

phil-d-wilson commented 2 years ago

@titouanc ah, yes, it could be! I'll run it up on my NUC and see what I find.

At the moment we don't have versioned images for our blocks - but we are addressing that.

Thanks for the patience. ;)

phil-d-wilson commented 2 years ago

@titouanc - sorry for the delay. I have managed to recreate it on a NUC, so I'll try and investigate what's happening here.

Phil

phil-d-wilson commented 2 years ago

@titouanc I've been hacking on this for hours, but I can't find anything more concrete than the issue being caused by the bump to Chromium v95. I'm testing pinning the version of Chromium to V90 which is working on all device types in testing.

phil-d-wilson commented 2 years ago

@titouanc I'm just pushing version 2.3.0 to dockerhub. Would you mind testing your end before I close this issue? I've tested it on Pi3, Pi4 and a NUC and it's working for me. I've also echo'ed the Chromium version to the logging.

This should really cut down on the potential issues caused when we push a new version of the block - however, we are implementing pinned versions of the blocks. The reason we are not doing this now on Dockerhub, is because we want to move away from using Dockerhub for the blocks and use the balena container registry instead. This is a WIP but it is a focus of our work right now.

titouanc commented 2 years ago

@phil-d-wilson I'll gladly do this as soon as it gets published to Dockerhub

phil-d-wilson commented 2 years ago

@titouanc hey mate - the version 2.3.1 is up on dockerhub. I'm grateful for the help with testing. :)

titouanc commented 2 years ago

I do not encounter the issue anymore, thank you for taking care of this @phil-d-wilson

phil-d-wilson commented 2 years ago

Thanks for the help @titouanc