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
In a readonly filesystem, in our case we have docker mounted as readonly, when importing splink it crashes trying to create __splinkdata_cache__
To Reproduce
In a docker image with splink installed the following command fails docker run --rm --read-only test python -c 'import splink'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/local/lib/python3.12/site-packages/splink/__init__.py", line 5, in <module>
from splink.internals.datasets import splink_datasets
File "/usr/local/lib/python3.12/site-packages/splink/internals/datasets/__init__.py", line 270, in <module>
class _SplinkDataSets(metaclass=_SplinkDataSetsMeta, datasets=_datasets):
File "/usr/local/lib/python3.12/site-packages/splink/internals/datasets/__init__.py", line 152, in __new__
cls.cache_dir.mkdir(exist_ok=True)
File "/usr/local/lib/python3.12/pathlib.py", line 1311, in mkdir
os.mkdir(self, mode)
OSError: [Errno 30] Read-only file system: '/usr/local/lib/python3.12/site-packages/splink/internals/datasets/__splinkdata_cache__'
OS:
linux
Splink version:
4.0.0
Have you tried this on the latest master branch?
I agree
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
I agree
The text was updated successfully, but these errors were encountered:
What happens?
In a readonly filesystem, in our case we have docker mounted as readonly, when importing splink it crashes trying to create
__splinkdata_cache__
To Reproduce
In a docker image with splink installed the following command fails
docker run --rm --read-only test python -c 'import splink'
OS:
linux
Splink version:
4.0.0
Have you tried this on the latest
master
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: