And do you run the website with the command develop.sh ?
danny225
yes
monkey
OK, thanks for the info. Let me think a minute about what could be the issue
danny225
Till database setup everything works fine
okay thanks
monkey
I can't think of anything obvious. But I do have a couple of suggestions:
1. Remove the container before trying again: run the command `docker rm -f bookbrainz-site` to remove it
2. Perhaps there is a file permission issue somewhere? If you are not using WSL (Windows Subsystem for Linux) I would suggest trying that. From the feedback I've gotten from Windows users this can solve some issues. See https://docs.docker.com/desktop/windows/wsl/
I'm sorry that's not a lot of help, I don't have a windows machine to test and can't tell what the issue is.
danny225
Thanks for the suggestions
I will try these. If again failed I will start on differnt OS through virtual box
monkey
Just another shot in the dark: can you please pass the entire contents of the config json into a json linter like this one? https://jsonlint.com/
danny225
On Linux it will work fine right
monkey
The WSL thing is basically using linux under the hood similar to a virtual machine, so hopefully you don't have to resort to a VM
danny225
Let me try these fixes. If you something helpful then please let me know...
Shubh
danny225: can you try running it without docker? , only dependencies in docker...
danny225
then EACESS error comes even after setting WSL 2
monkey
Ah, you get an EACESS error?
Can you paste the whole error text in a pastebin?
danny225
If not using docker
monkey
Well, that's a symptom of a permission issue, which coul dvery well cause the issue you see in Docker
That is an important clue
danny225
But in troubleshooting it is written setting WSL 2 will fix EACESS error
Shubh you are working on which OS
Shubh
Linux
monkey
It has helped some users in the past, yes, but there's no guarantee you the the same error or for the same reason :) Let's hope WSL solves you issue.
Otherwise, I would suggest focusing on figuring out why you get permission issues and trying to solve tthat. In turn that would hopefullyfix the same issue in docker