A big :+1: for running Docker containers with `--read-only`, forcing you to use explicit writeable volume/bind mounts for all writable data... it's not just the security benefits, you can also avoid entire classes of problems like:
* minimizing the difference between `docker restart` (preserves overlayfs changes) and container re-creates (resets overlayfs back to the image state)
* surprise data loss on container redeployments because data was unexpectedly being written to the overlayfs instead of a volume
* unexpectedly running out of disk space in `/var/lib/docker` because data was being written outside of a volume
* performance issues caused by excessive overlayfs writes (storage drivers and /var/lib/docker not necessarily designed for IO performance)