Closed ghost closed 2 years ago
In the lines below, why are the permissions of the folder changed before the folder even gets created? Where would the /data
folder be created otherwise (I do not use a mount for storing settings since I don't care about persistent mode)?
Any reason why this setup is not done in the dockerfile? Is it because some people mount a volume at that location? (EDIT: I oculd remove the "no such file or directory" error by creating the volume and biding it to /data
but the other issues remain.
Hi there @vbersier
I've just run up a new fleet with the browser block, on a Pi4 running OS 2.88.5+rev1 and everything works as expected:
As you can see, I can also run the GPU memory command fine. I don't think this is an issue with the block itself. You could ask for some more support on our forums, though, to see why your device isn't working as expected:
Why does it say this when i got to add a new device to my fleet?
Seems like something is not right with that version. Also, could it be that we do not use the same revision of the rpi4 board? I have an older 1.2 revision board.
Will create a new fleet now and test with only that browser container.
Confirmed working with a minimal setup and a new fleet. Will need to investigate
Turns out my problem is due to a conflict with another container that needs udev rules to enable access to USB storage devices.
I guess the fact that both containers are privileged means they can't access the same resources at the same time. It wasn't a problem with balenaplayground/balenalabs-browser
so I'm curious what changed.
Hey there,
Trying to run a browser on a rpi4 device running balenaOS (latest as of writing) 64-bit, freshly flashed onto the SD. The device is connected to a raspberry pi touchscreen via a ribbon cable. The old image from
balenaplayground/balenalabs-browser
was working fine with the touchscreen but I decided to upgrade since that one doesn't seem to exist anymore.Here's the docker-compose:
And here is the output below. It seems the
vcgencmd
tool is not working as expected and it can't determine the GPU memory (which is set to 512MB). This happens regardless if I specify the tag of the image as beingraspberrypi4-64
or not. When I ssh into the container and manually run the tool, I getLogs from the dashboard: