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
Gen AI demo deployed without any problems without RAG/Opensearch when try to enable RAG it gives this error.
#2 [internal] load metadata for quay.io/unstructured-io/unstructured:0.11.2
adilGenAIChatBotStack: success: Published 6a0e8f536c6289c4058cfb6e04c41fe51d83b7278274c46561a4d7e343f0f3f0:905862766196-us-west-2
#2 ERROR: unexpected status from HEAD request to https://quay.io/v2/unstructured-io/unstructured/manifests/0.11.2: 502 Bad Gateway
------
> [internal] load metadata for quay.io/unstructured-io/unstructured:0.11.2:
------
file-import-dockerfile:1
--------------------
1 | >>> FROM quay.io/unstructured-io/unstructured:0.11.2
2 |
3 | WORKDIR /app
--------------------
ERROR: failed to solve: quay.io/unstructured-io/unstructured:0.11.2: unexpected status from HEAD request to https://quay.io/v2/unstructured-io/unstructured/manifests/0.11.2: 502 Bad Gateway
adilGenAIChatBotStack: fail: docker build --tag cdkasset-e726015995d38bdadaf0f9ab6793508c5fe924a5f4bd74d1d55157045050484a --file file-import-dockerfile --platform linux/amd64 . exited with error code 1: #0 building with "default" instance using docker driver
The text was updated successfully, but these errors were encountered:
Hi @adlic, are you using Cloud9 for deploying the solution? If not, please check that the machine you are using can access quay.io - for example by running docker pull quay.io/unstructured-io/unstructured:0.11.2 from a terminal. If this command is not successful it means that you cannot use such machine to deploy the solution and we advice to follow the steps for using Cloud9 https://aws-samples.github.io/aws-genai-llm-chatbot/guide/deploy.html#deploy-with-aws-cloud9
Gen AI demo deployed without any problems without RAG/Opensearch when try to enable RAG it gives this error.
The text was updated successfully, but these errors were encountered: