Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Add ReadOnlyFs option to default execution parameters config #906

Open
PSanetra opened this issue Apr 16, 2022 · 1 comment
Open

Comments

@PSanetra
Copy link

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.

@PSanetra PSanetra changed the title Add ReadOnlyFs option to default execution parameters config Proposal: Add ReadOnlyFs option to default execution parameters config Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@PSanetra and others