-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
EACCES error when running cspell in a docker container #1510
Comments
Excellent report! |
Jason3S
added a commit
that referenced
this issue
Aug 13, 2021
I checked the code, it only logs the message it got from I put up a fix to clean up the log in #1512 |
Jason3S
added a commit
that referenced
this issue
Aug 13, 2021
Thank you :) |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Info
Kind of Issue
Which Tool or library
Which Version
Version:
5.6.6
Issue with supporting library?
OS:
version:
OS version if applicable.
Not sure if this is applicable, but the container is an
Alpine 3.14
and my actual machine is runningUbuntu 20.04
.Bug Description
Describe the bug
I have made a Dockerfile with Node 16.6.2 and when I run cspell (
cspell 'src/**/*.md'
) the below error is written to the console. The spellcheck is still performed, so this is more of a nuisance than anything else. I do have acspell.json
file in the directory from which I am running cspell.To Reproduce
Steps to reproduce the behavior:
I have a repository with the setup: https://github.com/pingvinen/cspell-eaccess-in-docker-container-issue
docker-compose
/bin/sh
or by triggered the npm script directlyExpected behavior
I would not expect it to complain, as there is a config file (
cspell.json
) in the same directory that I am running cspell from. When I try this exact same setup outside of the docker container (using the same cspell and node versions), cspell runs without that issue and I do not have a~/.config/configstore/cspell.json
file, so it is clearly not required to make the software work.Screenshots
Not relevant
Additional context
Nothing further to add.
cspell.json
This is also available in the example repository mentioned above, but here is a copy as well:
Example Repository (Optional)
https://github.com/pingvinen/cspell-eaccess-in-docker-container-issue
The text was updated successfully, but these errors were encountered: