Closed gerroon closed 9 months ago
Hmm, maybe it is not creating the /sist2-admin/scan-books-2024-01-12 21:23:56.984741.sist2
? Because I do not see such file in the actual container.
EDIT: adding a new tasks with sqlite backend works. So it seem like Elastic is broken in the docker container. Started a new task scanning with the sqlite backend. It will probably take a while.
The sqlite scan finished but I am unable to create the GUI entry for that scan. The indexer job is listed in the panel but I am unable to click on it so I cant create t.
Can you go to the job page and see what its status is? It will not be selectable until the status is "indexed"
Device Information (please complete the following information):
Hi
I am using the docker compose as is. So my documents path is
/host/mnt/z/books
I login tosist2-sist2-admin-1
to check if I can browse that path, and yes I can browse the path in the docker container. So I assumed that should be the actual path that I put in a task job that I created.I also tested elastic and the admin panel was able to connect to it.
It returns and error. It seems like it is the wrong path, but how could that be given I test that exact path in the running container?
docker compose