-
Notifications
You must be signed in to change notification settings - Fork 50
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
In version 1.7.2, ingestion doesn't seem to work, no container is created #73
Comments
Thanks for reporting this. In this version, the code actually expects to have a "general" profile in the secrets.toml file, but I see now that it's not represented in this way in the secrets.example.toml. I will fix this shortly to reflect, but in the meantime can you please add a single line as below to your secrets.toml file and see if that helps? [general] (this is kind of documented here: https://github.com/vectara/vectara-ingest?tab=readme-ov-file#configuration, above the summarize_table option, but not updated in the secrets.example.toml file) |
@ofermend My thanks for the clarification! ❤️ A couple more questions:
$ ./run.sh config/mywebsite-v3.yaml default
cp: cannot stat 'secrets.toml': No such file or directory
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Sending build context to Docker daemon 4.061MB
Step 1/35 : FROM --platform=linux/amd64 ubuntu:22.04
---> 174c8c134b2a
Step 2/35 : ENV DEBIAN_FRONTEND noninteractive
---> Using cache
---> 0f078248133b
... |
Hey Michael,
|
The first run talked about the
legacy builder
being deprecated, the--no-dev
option being deprecated and then failed withRead on closed or unwrapped SSL socket
...although the script still reportedSuccess! Ingest job is running.
After numerous runs (it kept installing new things), the ingestion script ran as normal (see output below). However, when I ran the command to check the ingestion status, the container wasn't in existence!
The text was updated successfully, but these errors were encountered: