Rasa: Docker run fails on startup

Created on 29 Mar 2018  路  4Comments  路  Source: RasaHQ/rasa

Rasa NLU version (e.g. 0.7.3): 0.12.0a2

Used backend / pipeline (spacy_sklearn, ...):Full

Operating system (windows, osx, ...): macos sierra

Issue: docker run doesn't start container but fails with error

Docker version : 18.03.0-ce

Command to start container:
docker run -p 0.0.0.0:5000:5000 rasa/rasa_nlu:latest-full

Error:

usage: server.py [-h] [-e {wit,luis,dialogflow}] [-P PORT] [-t TOKEN]
                 [-w WRITE] --path PATH [--cors [CORS [CORS ...]]]
                 [--max_training_processes MAX_TRAINING_PROCESSES]
                 [--num_threads NUM_THREADS] [--response_log RESPONSE_LOG]
                 [--storage STORAGE] [-c CONFIG] [--debug] [-v]
server.py: error: the following arguments are required: --path
type

All 4 comments

The current master build has a problem with the docker. Rasa expects the --path arguments.
You have two options to solve this

Option 1: Use my docker image

I have built a docker image with the latest rasa code you can use the command below
**Note : It requires a config file (yaml)

docker run -p 5000:5000 -v config.yaml:/app/config.yaml lomkju/rasa_nlu

Sample config yaml:

cors_origins:
- "*"
emulate: luis
project: myProject
fixed_model_name: myModel
pipeline: spacy_sklearn
num_threads: 4
port: 5000
path: projects

Option 2: Edit master code

You will need to clone the repo and build the docker image on your own. Change the server.py to the code below for the path argument.

    parser.add_argument('--path',
                        required=False,
                        help="working directory of the server. Models are"
                             "loaded from this directory and trained models "
                             "will be saved here.")

I've got a PR in for this #956

@ChamathK can you verify this is working for you know after pulling down a fresh image of latest? the. above PR was merged.

If not, let me know and we can open this one back up.

The issue is fixed @wrathagom . Many thanks.

Was this page helpful?
0 / 5 - 0 ratings