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 image: sqlite3.OperationalError: unable to open database file #57
Comments
Update (still not solved): I have confirmed path and permissions for the |
Hm. I'm not an expert in Docker myself, but I think you might be able to find out what's going wrong if you could get a shell inside your container. I have a script called 'dock' whose contents are:
This lets me get a shell inside a container by typing 'sudo dock' and its container ID. You could also just substitute the container ID into that command. To see the IDs of running containers, run |
Thanks for the reply. Nor me an expert in docker - I tend to use "real" vm's for manageability. I have tried:
-where
By issuing
I can attempt to ssh into port 22 and receive a userid/password prompt, but of course I have no info on appropriate credentials. Presumably someone must have built this image, and therefore have info on how to access the image? It is not sensible for me to keep guessing at how to access the image and using what credentials, that is not productive (to put it politely). |
I built the image. I can promise you that it has If I run this command:
I get a shell. Running If I ask for a file that doesn't exist, such as
The images were built with Docker 1.3 but I've been able to run them on 1.7. I don't think trying to hack into Docker through open ports is going to be productive at all. I have my doubts that what you're reaching is even the container. It might be something else internal to Docker. The container does not open any ports except for 10054. It's not running an SSH server. It's not running any processes except for The symlink that was necessary to patch a particular non-Docker version of 5.3 is not necessary. Here's how I can confirm that the DB exists where it's supposed to inside the container:
So, all I can say is that something is extremely messed up about your filesystem in Docker. Not only is it not finding |
Thanks for the python snippet, that may be helpful in the future if I can ever get a cli. Here's versioning for the record:
What is confusing me is that this set up is all entirely default; the only exception being that I have placed the docker image in a non-standard location as suggested here, following the '-g option' instructions here. However, I am beginning to suspect that changing the docker image installation directory like that may not compatible with this image, meaning that it would not be possible to locate the docker image also on a In case anyone else ends up in this dark place, here is a link to the docker forums post. |
Update (not solved). In case anyone is following this thread, I have posted docker daemon debug messages here |
I have built docker image with Ubuntu 14.04, Docker version 1.9.0, build 76d6bc9
I hope this can help you. |
Thank you for the update & instructions. I may try this at some point; though right now my plan when I can get back to this project is to build from scratch. For the record I have received exactly zero responses to my request for help on the docker forums; it seems their focus is solely on for-profit support contracts. |
Dear @cwynd However, I have the same problem I think. When I want to make a query, for example [http://localhost:10054/data/5.4/c/en/toast] it gives me this error |
Facing same issue. Any solution found? |
Hi, I have followed the Docker instructions here:
https://github.com/commonsense/conceptnet5/wiki/Docker#building-conceptnet-with-docker
and this proceeded error-free.
I can run the container and see the following log:
However if I then try an example query:
http://127.0.0.1:32768/data/5.4/c/en/toast
I get a 500 internal server error:
-which looks like it may be the same underlying error as this:
#33
I have tried to figure out how to get a shell on the container so I can try the 'ln -s' fix, but have had no success.
Would appreciate any help or advice on
-how to access the container and try the above fix myself, or
-otherwise how to resolve the issue.
Thanks in advance for any advice!
The text was updated successfully, but these errors were encountered: