unknown flag: --config Error

[shiva4983]

Hi Team,

When I pass the proxy details using --config. I got unknown flag error. Kindly let me know how to fix it.

Thanks, Siva

[devalex88]

Hi. Sorry for the late response. Could you please share the full log?

[shiva4983]

Hi, Since I am running using Windows command prompt, the bash window closes immediately. Couldn't paste the log. my run_firefox.sh is having

!/usr/bin/env bash

set -xe

current_dir=$(pwd) project_dir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" reports_dir="$( cd "$( dirname "${BASH_SOURCE[0]}" )/.." && pwd )/reports/firefox"

rm -rfv "$reports_dir" mkdir -p "$reports_dir"

katalon_opts='-browserType="Firefox" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/Admin - WorkFlow Sprints"' docker run --rm -v "/$project_dir":/katalon/katalon/source:ro -v "/$reports_dir":/katalon/katalon/report -e KATALON_OPTS="$katalon_opts" --config -proxy.option="MANUAL_CONFIG" -proxy.server.type="HTTP" -proxy.server.address=http://myproxy.net -proxy.server.port=8080 -proxy.username=myProxyUserName -proxy.password=myProxyPassword katalonstudio/katalon

cd $current_dir

When I run from Command Prompt. Bash window open and try to run the docker command and finally shows unknown flag: --config See 'docker run --help'

[shiva4983]

Hi, Any update??

[shiva4983]

@devalex88 Any update?

[jejey]

hello, why don't you use docker quick start terminal ? Have you tried using it ? ( with boot2docker included)

[devalex88]

@shiva4983,

I'm sorry for the late response. The script should be

katalon_opts='-browserType="Firefox" -retry=0 -statusDelay=15 -testSuitePath="Test Suites/Admin - WorkFlow Sprints" --config -proxy.option="MANUAL_CONFIG" -proxy.server.type="HTTP" -proxy.server.address=http://myproxy.net -proxy.server.port=8080 -proxy.username=myProxyUserName -proxy.password=myProxyPassword'
docker run --rm -v "/$project_dir":/katalon/katalon/source:ro -v "/$reports_dir":/katalon/katalon/report -e KATALON_OPTS="$katalon_opts" katalonstudio/katalon

I realize that this is a bug in our README. It has been corrected.

[shiva4983]

Thanks @devalex88.