Error running Taurus using Docker image through GitLab CI

[Nick Gover]

I'm running into an error that I can't seem to find much information on.  I'm trying to run Taurus from my gitlab-ci.yml configuration using the published "blazemeter/taurus" docker image.

The error references an option "-c" that is not found. Which I'm not referencing. However, It seems like it fails before I even attempt to run any scripts.  I'm not sure what is missing.

I've tried multiple tags 

Here is an example of the .gitlab-ci.yml

image: blazemeter/taurus:1.13.8

stages:

 - test

before_script:

- echo "before test stage"

test:

 stage: test

 script:

  - ./bzt taurus.yml

after_script:

 - echo "End CI"

And an example of the Console output:

Running with gitlab-runner 12.3.0 (a8a019e0)
  on docker-auto-scale 0277ea0f
Using Docker executor with image blazemeter/taurus:1.13.9 ...
Pulling docker image blazemeter/taurus:1.13.9 ...
Using docker image sha256:cfd94d78c915076204616fb4d2b5f6fa2e41c83899ee22741373a2dc1bf83417 for blazemeter/taurus:1.13.9 ...

Running on runner-0277ea0f-project-9664807-concurrent-0 via runner-0277ea0f-srm-1571792804-e94c7285...

Fetching changes...
Initialized empty Git repository in /builds/jnickgo/taurus-test/.git/
Created fresh repository.
From https://gitlab.com/jnickgo/taurus-test
 * [new ref]         refs/pipelines/90753469 -> refs/pipelines/90753469
 * [new branch]      master                  -> origin/master
Checking out bbbceef0 as master...

Skipping Git submodules setup

Usage: bzt [options] [configs] [-aliases]

bzt: error: no such option: -c

Usage: bzt [options] [configs] [-aliases]

bzt: error: no such option: -c

ERROR: Job failed: exit code 2

[grey....@gmail.com]

Hello.

Vague case, could you simplify it? 

First of all I recommend to check local installation, then docker and eventually gitlab. Anyway, artifacts (especially bzt.log) are strongly appreciated, it's hard to guess the cause without them. 

---

Taras

[Nick Gover]

I'll try to get the log.

It works fine locally, it also works fine if I take a different image with Java and python and just install bzt. It just doesn't work with the blazemeter/taurus image.

It's pretty simple, it's only running a single command and it blows up before ever making it to the stage that runs the bzt command.

[Nick Gover]

Oddly enough, if I try a different image it works fine.  So, maybe an issue with the blazemeter/taurus image or I'm using it wrong. See below.

example of gitlab-ci.yml file with a different image.  This worked fine the first try

image: openkbs/jre-mvn-py3:latest

stages:

 - test

test:

 stage: test

 script:

  - sudo pip install bzt

  - bzt taurus.yml -q -o modules.cloud.token=${BLAZE_PUBLIC_KEY}:${BLAZE_SECRET_KEY}

[maxim....@blazemeter.com]

doesn't work with the  blazemeter/taurus image.

Hello, could you please show log file, yaml configuration file and command used to start all this staff? 

---

Maks