Is there an argument to add to docker-compose.override.yml when starting Rasa X to ensure that debug information is printed in the logs? I want to see why my “app” and “production” containers are giving me issues…
Yes, if you take a look at the existing command
entry in the docker-compose.yml
and add the --debug
option that would do it. The docker-compose.override.yml
would add these entries:
rasa-production:
command: >
x
--no-prompt
--production
--config-endpoint http://rasa-x:5002/api/config?token=${RASA_X_TOKEN}
--port 5005
--jwt-method HS256
--jwt-secret ${JWT_SECRET}
--auth-token '${RASA_TOKEN}'
--cors "*"
--debug
rasa-worker:
command: >
x
--no-prompt
--production
--config-endpoint http://rasa-x:5002/api/config?token=${RASA_X_TOKEN}
--port 5005
--jwt-method HS256
--jwt-secret ${JWT_SECRET}
--auth-token '${RASA_TOKEN}'
--cors "*"
--debug
1 Like
In the new versions of Rasa X, the commands are spelled out in a ‘default-rasa-service’ block. I added the ‘–debug’ statement to this block as below:
x-rasa-services: &default-rasa-service
restart: always
image: "rasa/rasa:${RASA_VERSION}-full"
expose:
- "5005"
command: >
x
--no-prompt
--production
--config-endpoint http://rasa-x:5002/api/config?token=${RASA_X_TOKEN}
--port 5005
--jwt-method HS256
--jwt-secret ${JWT_SECRET}
--auth-token '${RASA_TOKEN}'
--cors "*"
--debug
depends_on:
- rasa-x
- rabbit
- redis
However, the logs in docker do not reflect any debug information in the production container or the worker container. Is it possible to verify and add debug information as a default output for Docker environments? It’s super unclear in the default docker compose setup:
- when models are training and what stage they are in training
- action server debug info
Docker logs still don’t carry full debug information that a command like ‘rasa shell debug’ gives.