You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since you can specify the target host on the Locust class I don't see a need to having to specify it again with an environment variable. Could this restriction be removed, or am I missing something?
The text was updated successfully, but these errors were encountered:
I agree. The Docker image should not require any environment variables. I'm not sure if it's a good idea to have the shell script that constructs the command line arguments for locust at all.
However there's an easy workaround. Just specify locust [arguments] as the COMMAND for docker run.
Just specify locust [arguments] as the COMMAND for docker run.
But you still need arguments to make it run correctly. Env vars are one quite regular way of doing this.
I think perhaps we should set /usr/local/bin/locust as the ENTRYPOINT and leave CMD unset. This is quite conventional and means the user must pass all required arguments to docker run, e.g:
Since you can specify the target host on the Locust class I don't see a need to having to specify it again with an environment variable. Could this restriction be removed, or am I missing something?
The text was updated successfully, but these errors were encountered: