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

feat: support running on a read-only filesystem #131

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

paulswartz
Copy link
Contributor

Docker containers can run on a read-only filesystem, which has some security benefits. The current updater implementation writes the .tgz file to the filesystem, so it does not work in such an environment.

This provides a read_only_fs? configuration which stores the data in memory while loading, and does not write the ETS table to disk for future loading.

@paulswartz paulswartz force-pushed the read-only branch 4 times, most recently from 2811a30 to 9bd96ae Compare December 27, 2022 17:02
@paulswartz
Copy link
Contributor Author

Docker containers can run on a read-only filesystem, which has some
security benefits. The current updater implementation writes the .tgz
file to the filesystem, so it does not work in such an environment.

This provides a `read_only_fs?` configuration which stores the data in
memory while loading, and does not write the ETS table to disk for
future loading.
@paulswartz
Copy link
Contributor Author

Rebased on top of the latest master, and remove the other implementation of the GitHub CI.

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

Successfully merging this pull request may close these issues.

1 participant