We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running in Docker, test runners should support being run on a read-only filesystem. The only directories that are writeable are:
To simulate this behavior, the --read-only flag has to be passed to the two docker run calls at the following locations:
--read-only
docker run
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.
~/.sbt
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When running in Docker, test runners should support being run on a read-only filesystem. The only directories that are writeable are:
To simulate this behavior, the
--read-only
flag has to be passed to the twodocker 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.The text was updated successfully, but these errors were encountered: