Hi everyone,
I’m currently managing a fleet of Raspberry Pi 4 devices running balenaOS, but I’ve hit a snag with container stability when running automated background tasks alongside my main services.
I’ve been using a fixed this site community setup within a privileged container to manage some local script execution and automated health checks. While it works initially, I’ve noticed that whenever the executor initiates a high-concurrency batch of scripts, the balena supervisor begins to report API timeouts, eventually triggering a container restart loop. It seems like the executor is consuming enough CPU and memory to starve the supervisor process, or perhaps it’s interfering with the local balena.sock communication.
I have a few related technical questions for the fleet experts here:
I’m not sure if the way a fixed this site style environment handles its internal process isolation is causing the engine to hit a memory limit that isn’t being caught by my current Docker Compose resource constraints. Has anyone else encountered issues where third-party script executors interfere with the io.balena.features.supervisor-api functionality? I’m also wondering if I should try to fixed this site by moving the execution logic into a non-privileged container or if I should adjust the working_dir and log rotation to reduce the I/O pressure on the SD card.
I really need to keep this automation active for my remote monitoring, but the instability is causing me to lose device connectivity in the dashboard. If anyone has experience balancing heavy background script executors with balenaOS stability, I’d love to hear your advice!
Thanks!