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
Seems like docker-compose-standalone-nlu.yaml from examples/docker-compose doesn't work as expected - it doesn't use standalone NLU server that is running in a separate container botpress-nlu
⚠️ File docker-compose-standalone-nlu.yaml was last updated 3 years ago, but it's still in master brach, that's why I decided to draw attention to this problem.
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/botpress/v12.git
cd v12/examples/docker-compose
mkdir -m 777 botpress/data botpress/language
sed -i 's/GET_LATEST_FROM_DOCKERHUB/latest/' botpress/Dockerfile
docker compose -f docker-compose-standalone-nlu.yaml up -d
In the output of docker top botpress-server you will see:
In the output of docker logs botpress-server you will see something like:
03/18/2024 01:17:32.592 Server Started in 1291ms
03/18/2024 01:17:33.770 [NLU] Launcher ===========================================================================
Botpress Standalone NLU
Version 1.0.2 - Build 20220909-2040_BIN
===========================================================================
03/18/2024 01:17:33.773 [NLU] Launcher Loading config from environment variables
03/18/2024 01:17:33.774 [NLU] Launcher limit: disabled (no protection - anyone can query without limitation)
03/18/2024 01:17:33.774 [NLU] Launcher duckling: enabled url=http://localhost:8000 03/18/2024 01:17:33.775 [NLU] Launcher lang server: url=https://lang-01.botpress.io
03/18/2024 01:17:33.776 [NLU] Launcher body size: allowing HTTP requests body of size 2mb
03/18/2024 01:17:33.776 [NLU] Launcher models stored at "/botpress"
03/18/2024 01:17:33.776 [NLU] Launcher batch size: allowing up to 1 predictions in one call to POST /predict
03/18/2024 01:17:34.429 [NLU] Launcher NLU Server is ready at http://localhost:3200/. Make sure this URL is not publicly available.
(node:86) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
03/18/2024 01:17:34.909 [Messaging] Launcher ===========================================================================
Botpress Messaging
Version 1.2.15
===========================================================================
(marked important strings bold)
Expected behavior
The output of docker top botpress-server shouldn't contain /botpress/bin/nlu
The output of docker logs botpress-server shouldn't contain url=https://lang-01.botpress.io, lang server must be http://botpress_nlu:3200
Screenshots
Environment (please complete the following information):
OS: Ubuntu 22.04.4 LTS
docker 25.0.4, build 1a576c5
docker-compose v2.24.7
Botpress v12.31.5 (docker run botpress/server ./bp version)
NodeJS: v12.18.1 (docker run botpress/server ./bp version)
pavelsr
changed the title
Seems like examples/docker-compose/docker-compose-standalone-nlu.yaml
docker-compose-standalone-nlu.yaml not working as expected
Mar 18, 2024
Describe the bug
Seems like
docker-compose-standalone-nlu.yaml
fromexamples/docker-compose
doesn't work as expected - it doesn't use standalone NLU server that is running in a separate containerbotpress-nlu
To Reproduce
Steps to reproduce the behavior:
In the output of
docker top botpress-server
you will see:In the output of
docker logs botpress-server
you will see something like:(marked important strings bold)
Expected behavior
The output of
docker top botpress-server
shouldn't contain/botpress/bin/nlu
The output of
docker logs botpress-server
shouldn't containurl=https://lang-01.botpress.io
, lang server must behttp://botpress_nlu:3200
Screenshots
Environment (please complete the following information):
docker run botpress/server ./bp version
)docker run botpress/server ./bp version
)Additional context
@laurentlp, @daehli, @charlescatta, @Michael-N-M, @allardy, as contributors of this docker files, please have a look
The text was updated successfully, but these errors were encountered: