Lean CLI "docker run" command

Hi, what is the docker command that "lean backtest" command runs? I'm trying to run it manually so I can configure it with other docker services. I tried to get the "docker run" command with the tool mentioned here which gives me the following, but it didn't give the same output.

docker run `
--name=lean_cli_vsdbg `
--hostname=COMPUTER-01 `
--mac-address=02:a2:cf:81:00:02 `
--env=DOTNET_NOLOGO=true `
--env=DOTNET_CLI_TELEMETRY_OPTOUT=true `
--env=PATH=/opt/miniconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin `
--env=DEBIAN_FRONTEND=teletype `
--env=LANG=en_US.UTF-8 `
--env=LANGUAGE=en_US:en `
--env=LC_ALL=en_US.UTF-8 `
--env=CONDA=Miniconda3-4.5.12-Linux-x86_64.sh `
--env=PIP_DEFAULT_TIMEOUT=120 `
--env=PYTHONNET_PYDLL=/opt/miniconda3/lib/libpython3.6m.so `
--volume='C:\Projects\lean-cloud\data:/Lean/Data:rw' `
--volume='C:\Projects\lean-cloud\proj\backtests\2021-06-08_21-38-27:/Results:rw' `
--volume='C:\Projects\lean-cloud\proj\storage:/Storage:rw' `
--volume='C:\Users\user\AppData\Local\Temp\lean-cli-chpf547q:/LeanCLI:rw' `
--volume=lean_cli_nuget:/root/.nuget/packages:rw `
--volume=/Lean/Data `
--volume=/LeanCLI `
--volume=/Results `
--volume=/Storage `
--volume=/root/.nuget/packages `
--workdir=/Lean/Launcher/bin/Debug `
--detach=true `
-t quantconnect/lean:latest
+ Expand
- Collapse

One suggestion: If you can include the "docker run" command in the --verbose switch that would be great.

Thanks,
Omid

docker run `
--env=DOTNET_NOLOGO=true `
--env=DOTNET_CLI_TELEMETRY_OPTOUT=true `
--hostname=My-Computer `
--stop-signal="SIGINT" `
--volume="C:/Users/Username/AppData/Local/Temp/lean-cli-9flv5wjb/config.json:/Lean/Launcher/bin/Debug/config.json" `
--volume="C:/Users/Username/AppData/Local/Temp/lean-cli-d1846bsr/lean-cli-start.sh:/lean-cli-start.sh" `
--volume="C:/Users/Username/AppData/Local/Temp/lean-cli-rc7d5wy2:/LeanCLI" `
--volume="C:/Projects/LeanCLI/data:/Lean/Data" `
--volume="C:/Projects/LeanCLI/CSharp Project/backtests/2021-06-09_15-27-21:/Results" `
--volume="C:/Projects/LeanCLI/CSharp Project/storage:/Storage" `
--volume="lean_cli_nuget:/root/.nuget/packages" `
--entrypoint="bash" `
quantconnect/lean:latest `
/lean-cli-start.sh

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.

Great, I tried it and it worked with minor modifications. My trick to keep temporary directories from being removed too quickly was to press the pause button on the keyboard after running “lean backtest”. :) I only needed to modify $\leq a n - c l i - ⋆ t . s h$ $lean-cli-start.sh$ and add $c p \frac{}{L} e a n C L \frac{I}{b} \frac{\in}{D} e b u \frac{g}{\cdot} . d l l \frac{}{L} e a \frac{n}{L} a u n c h e \frac{r}{b} \frac{\in}{D} e b u \frac{g}{}$ $cp /LeanCLI/bin/Debug/*.dll /Lean/Launcher/bin/Debug/$ to it after $\dot{\neq} t b u i l d$ $dotnet build$ line, otherwise I got a FileNotFoundException. I don't know how it works in Lean CLI without copying project DLL to the Launcher's bulid path.

Omid Rad INVESTOR

June 2021

Upvote

Jasper van Merle INVESTOR

Hi Omid,

The CLI generates a custom .csproj file before building C# projects. In this .csproj file $O u t p u t P a t h$ $OutputPath$ is set to $/ L e a \frac{n}{L} a u n c h e \frac{r}{b} \frac{\in}{D} e b u g$ $/Lean/Launcher/bin/Debug$ and $C o p y L o c a l L o c k F i \leq A s s e m b l i e s$ $CopyLocalLockFileAssemblies$ is set to true, so running $\dot{\neq} t b u i l d$ $dotnet build$ automatically places the DLL files for the project and all referenced libraries in that directory. You can find the full contents of the generated .csproj file on GitHub.

1 person upvoted this

Excellent! Thanks so much for your help. 👍

Platform

Radically Open-Source Algorithmic Trading Engine

Join Our Discord Channel

Quarterly Open-Source Trading Competition

Draft Discussions

Bookmarked Discussions

SEARCH DISCUSSIONS

373,800 Quants.

VOTE FOR UPCOMING FEATURES

JOIN OUR Community MAILING LIST

IN THIS RESEARCH

PARTICIPANTS

Actions

Join QuantConnect for Free