You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to extend the default execution parameters config with a ReadOnlyFs field. Currently it is only possible to declare that option explicitly on container start (e.g. with docker run --read-only). It would be better if the image author could declare this option already during the image build as the author has more knowledge about the fact if the container needs a writable filesystem at runtime or not.
Another problem with declaring the read-only option separately from the image (e.g. in a Helm chart for Kubernetes deployment) is that the requirement for a writable filesystem may change with a new image release.
The text was updated successfully, but these errors were encountered:
PSanetra
changed the title
Add ReadOnlyFs option to default execution parameters config
Proposal: Add ReadOnlyFs option to default execution parameters config
Apr 16, 2022
It would be nice to extend the default execution parameters config with a
ReadOnlyFs
field. Currently it is only possible to declare that option explicitly on container start (e.g. withdocker run --read-only
). It would be better if the image author could declare this option already during the image build as the author has more knowledge about the fact if the container needs a writable filesystem at runtime or not.Another problem with declaring the read-only option separately from the image (e.g. in a Helm chart for Kubernetes deployment) is that the requirement for a writable filesystem may change with a new image release.
The text was updated successfully, but these errors were encountered: