Thanks to @KStephen1991, I’ve created action image. Here is what I’ve done:
- Dockerfile:
FROM rasa/rasa-sdk:latest
USER root
WORKDIR /app
RUN pip3 install grakn.client
COPY ./actions /app/actions
COPY ./grakn_kg.py /app/grakn_kg.py
COPY ./data/nlu.md app/data/nlu.md
COPY ./data/stories.md app/data/stories.md
COPY ./data/jieba_userdict_zh.txt app/data/jieba_userdict_zh.txt
COPY ./data/total_word_feature_extractor_zh.dat app/data/total_word_feature_extractor_zh.dat
CMD ["start", "--actions", "actions"]
Notes: In the actions folder, there is only actions.py file, the grakn_kg.py is outside of the actions folder, otherwise, the rasa can’t find it when need to import it to actions.py.
- docker-compose.override.yml as below:
version: '3.4'
services:
app:
image: 'rasa-ticket:latest'
- then run
docker run rasa-ticket:latest
it shows
seems right. However, after run
sudo docker-compose up -d
It’s still not working for my bot.
My question NOW is how to test and justify the action image? @akelad @Tobias_Wochinger
What I can think of is to test compare it with rasa run command and rasa shell. As you can see below, the right panel is about rasa shell, the left up is image, the left down is rasa run; when first run “rasa run actoin”, the behavior is correct, however when run image, there’re errors ( Couldn’t connect to the server at ‘http://localhost:5055/webhook’ ):
The image behavior is different from “rasa run actions”.
Any clue to fix the problem?
Thanks for your attention!