The i.MX6S is on the lower end memory wise of all our compatible Torizon hardware. I’ll admit that some of the examples we put up may not have been designed for/tested with all of the range of hardware in mind. If possible could you clear all docker images and docker containers off the system that aren’t relevant to the grafana example. Then after you have a clean system, run the example again and try to monitor the memory usage during the process of possible. If this still fails then it might be a case of this sample wasn’t well tested on the lower end hardware. In which case sorry for the inconvenience but thank you for the letting me know, so we can do a better job of testing samples or marking them for hardware limitations.
If you ran docker system prune then that should have done what I asked of you. I did some additional testing on my own and spoke internally with the team and it appears that this is just a hardware limitation with the i.MX6S. We’ll try and do a better job of checking our samples and guides on the low-end of our modules.
While I still think it’s possible to have a Torizon system on the i.MX6s, you do have to be a lot more mindful about resource usage and the design of your application.
Currently I just checks different modules to see which one will fit a new product best.
I just started with the smallest one, to see when I reach the limit. I gues I did now
