Hi,
It looks like there is a script in your firefox container that tries to remove the entirety of the /tmp directory. This does not work for balena, as the Supervisor bind mounts a subdirectory under /tmp on host into /tmp/balena in container for the purpose of inter-container communication via update locks, see Update locks - Balena Documentation . As I’m not sure what the need for clearing the /tmp directory in container is, I’d recommend trying to get the contents of 10-clean-tmp-dir.sh as well as its surrounding script context to see what it’s needed for and whether you can remove the dependency yourself. Since the container you’re trying to run exits soon after each start, you may take a snapshot of the container with balena commit (which functions the same as docker commit) in order to get a snapshot image. You can then explore the snapshot with balena run --rm -it SNAPSHOT_IMAGE in order to see the startup order of scripts. Alternatively, if you do not wish to try to remove the dependency on the tmp script yourself, you can open an issue on the jlesage/firefox GitHub repo to ask the maintainers directly what the purpose of the /tmp directory is and whether it’s possible to not purge it on startup.
Let us know how that goes!
Thanks,
Christina