Limitations of image-based deployments
While image-based deployments are a paradigm shift in how we can create and maintain solutions, they do have idiosyncrasies that standard package-based deployments do not have. For image-based systems, updates happen at the speed of a reboot. Package-based systems’ update operations can take hours and require multiple reboots, all while hoping no dependencies are broken and everything works in the end.
One significant perceived limitation is that filesystems are defined as non-writable. While many see the broader concept of immutability as a feature, if you are trying to install a third-party solution into your image and said solution expects to be installed in a very specific location (filesystem) that is readable and writable, but the actual location is read-only, issues are instantaneous.
This is a perceived limitation, not an actual one. With some creative usage of symbolic links, this most likely can easily be circumvented.
...
