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

Support read-only file system #11

Open
ErikSchierboom opened this issue Apr 14, 2021 · 0 comments
Open

Support read-only file system #11

ErikSchierboom opened this issue Apr 14, 2021 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@ErikSchierboom
Copy link
Member

When running in Docker, test runners should support being run on a read-only filesystem. The only directories that are writeable are:

  • The /opt/test-runner directory
  • The /tmp directory
  • The input directory
  • The output directory

To simulate this behavior, the --read-only flag has to be passed to the two docker run calls at the following locations:

I've briefly looked into this, and the main problem seems to be that SBT is trying to write a lock file in the ~/.sbt directory.

@ErikSchierboom ErikSchierboom added the help wanted Extra attention is needed label Apr 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant