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
Docker document startup procedure for windows (permissions issue) #1061
Comments
Hi, thanks for the report, that validate-fns file was recently added, but I was not able to reproduce this on a fresh clone with |
I just ran it through Docker container |
I really want to help, but I would need you to tell me the steps you used to get this error. Are you running it in command line? Or through some hosting service? If you followed the steps here and it didn't work then we can fix it. If there's something else you did that should be supported, then we would like to amend the instructions and get that working. |
Ok I hadn't heard about this thing before, apparently it's called Docker Desktop I attempted to get docker desktop to run on my machine and failed, so please try running this via the currently supported command line instructions linked above, using docker-compose Maybe if you can figure out why it's broken for Docker Desktop then it'll benefit others that use that. |
THIS IS FROM VSCODE TERMINAL : PS C:\Users\Genny\UsTaxes> docker-compose up Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
|
THIS IS FROM GIT $ docker-compose up |
THIS IS CMD C:\Users\Genny\UsTaxes>docker-compose up
C:\Users\Genny\UsTaxes>no configuration file provided: not found |
@genesisoliva thanks for the logs, I'm seeing the same issues with docker desktop |
I got it to run, but when I open it in the browser it gives me a "This page isn’t working localhost didn’t send any data. |
PS C:\Users\Genny\UsTaxes> docker-compose build
|
That file https://stackoverflow.com/questions/48240635/data-permissions-docker-for-windows If you can figure out a way to fix this so that future windows users don't have this problem it would be appreciated. Or else I suppose it should be added to the docker section in the readme. |
This issue is not specific to Windows or docker desktop. I can recreate this on Manjaro/docker engine 23.0.1 with a clone from the most recent commit on master, 20022. The docker compose file is bind mounting the source files, which will set the ownership to root:root inside of the running container. See this issue in the moby repo which I believe is the cause of the permissions issues we are seeing. I submitted a PR which removes the bind mount from docker-compose.yml, and RUNS This is working on Windows 10 and Manjaro 5.15. I can test on some Ubuntu versions as well if it is helpful. This solution may negatively affect people who use the docker-compose file for development work. I have some thoughts on ways to build the docker image and use a dev container to meet the needs of users who just need to run the app and developers who want to mount the source files and get real time feedback. I will try to get on discord per the contributing doc and chat more about that later this week, but any thoughts you can provide here in an asynchronous manner would be preferential for me. |
Error: EACCES: permission denied, open 'src/core/data/validate-fns.js'
app_1 | at Object.openSync (node:fs:585:3)
app_1 | at Object.writeFileSync (node:fs:2153:35)
app_1 | at Object. (/home/node/app/scripts/setup.ts:67:4)
app_1 | at Module._compile (node:internal/modules/cjs/loader:1101:14)
app_1 | at Module.m._compile (/home/node/app/node_modules/ts-node/src/index.ts:1455:23)
app_1 | at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
app_1 | at Object.require.extensions. [as .ts] (/home/node/app/node_modules/ts-node/src/index.ts:1458:12)
app_1 | at Module.load (node:internal/modules/cjs/loader:981:32)
app_1 | at Function.Module._load (node:internal/modules/cjs/loader:822:12)
app_1 | at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12) {
app_1 | errno: -13,
app_1 | syscall: 'open',
app_1 | code: 'EACCES',
app_1 | path: 'src/core/data/validate-fns.js'
app_1 | }
The text was updated successfully, but these errors were encountered: