I’m still struggling to understand what advantage Docker brings to the set-up.
Maybe the application doesn’t need to write anything to disk at all (which seems unlikely) but if so, then you’re not saving any disk-write cycles by using docker.
Or maybe you want it only to write to filesystems mounted from longer-life storage e.g. magnetic disk and mark the SD card filesystems as --read-only. In which case you could mount those filesystems directly in the host OS (indeed you have to do this to make them visible to docker) and configure the app to use those directly, no need for docker.
Docker has many great features, but at the end of the day it’s just software - it can’t magic away some of the foundational limitiations of system architecture.
I think you still don’t get the idea of read-only containers.
They’re set up in a way that prohibits any writes except some very well defined locations. That could mean piping logs directly to stdout and don’t write them to disk, or not caching on disk, etc.
That is standard practice in professional setup (though for security reasons).
No, it’s not magic, but software can get configured, you know? And if you do that properly, you might see a change in behavior.
I’m still struggling to understand what advantage Docker brings to the set-up.
Maybe the application doesn’t need to write anything to disk at all (which seems unlikely) but if so, then you’re not saving any disk-write cycles by using docker.
Or maybe you want it only to write to filesystems mounted from longer-life storage e.g. magnetic disk and mark the SD card filesystems as --read-only. In which case you could mount those filesystems directly in the host OS (indeed you have to do this to make them visible to docker) and configure the app to use those directly, no need for docker.
Docker has many great features, but at the end of the day it’s just software - it can’t magic away some of the foundational limitiations of system architecture.
I think you still don’t get the idea of read-only containers.
They’re set up in a way that prohibits any writes except some very well defined locations. That could mean piping logs directly to stdout and don’t write them to disk, or not caching on disk, etc.
That is standard practice in professional setup (though for security reasons).
No, it’s not magic, but software can get configured, you know? And if you do that properly, you might see a change in behavior.
If the application in question doesn’t need to write anything, it also doesn’t write outside of docker, so it also won’t wear down the SD card.
If the app has to write something, a fully read-only container will simply not work (the app will crash or fail otherwise).