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
If you run the docker container for the very first time as suggested by the README (see chunk below), the container seems to start by downloading the language model itself. I think that it is important that the container is not queried while doing so as otherwise, the download seems to be interrupted, leading to an unusable setup. Waiting for a couple of minutes in the first start up seemed to work for me, at least.
I am not sure if this is a general problem, but maybe a hint in the README that the container might be ready to use only after a few minutes if you use it for the first time might be useful for other users as well.
The text was updated successfully, but these errors were encountered:
ChristophLeonhardt
changed the title
Perhaps suggest waiting period when the dbpedia spotlight docker container run the first time
Perhaps suggest waiting period when the dbpedia spotlight docker container is run for the first time
Nov 9, 2023
You need the Container ID for this command. So to prepare querying the container like this, I included getting the Container id from calling docker container ls in dbpedia_spotlight_status().
If you run the docker container for the very first time as suggested by the README (see chunk below), the container seems to start by downloading the language model itself. I think that it is important that the container is not queried while doing so as otherwise, the download seems to be interrupted, leading to an unusable setup. Waiting for a couple of minutes in the first start up seemed to work for me, at least.
dbpedia/README.Rmd
Lines 48 to 53 in 01c5d91
I am not sure if this is a general problem, but maybe a hint in the README that the container might be ready to use only after a few minutes if you use it for the first time might be useful for other users as well.
The text was updated successfully, but these errors were encountered: