文化
有很多朋友跟我說，在 Windows 上看過你文章知道了怎么抓 Crash, CPU爆高，內存暴漲 等各種Dump，為什么你沒有寫在 Docker 中如何抓的相關文章呢？瞧不上嗎？
(資料圖片僅供參考)
哈哈，在DUMP的分析旅程中，跑在 Docker 中的 .NET 占比真的不多，大概10個dump有 1-2 個是 docker 中的，市場決定了我的研究方向，為了彌補這一塊的空洞，決定寫一篇文章來分享下這三大異常下的捕獲吧。
二：Docker 下的三大異常捕獲1. crash dump 捕獲前不久我寫了一篇 Linux 上的 .NET 崩潰了怎么抓 Dump （https://www.cnblogs.com/huangxincheng/p/17440153.html）的文章，使用了微軟推薦的環境變量方式，其實這在 Docker 中是一樣適用的。
為了讓 webapi崩潰退出，我故意造一個棧溢出異常，參考代碼如下：
public class Program { public static void Main(string[] args) { var builder = WebApplication.CreateBuilder(args); builder.Services.AddAuthorization(); var app = builder.Build(); app.UseAuthorization(); //1. crash Task.Factory.StartNew(() => { Test("a"); }); app.Run(); } public static string Test(string a) { return Test("a" + a.Length); } }有了代碼之后，接下來寫一個 Dockerfile，主要就是把三個環境變量塞進去。
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS runtimeWORKDIR /appCOPY ./ ./# 1. 使用中科大鏡像源RUN sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" /etc/apt/sources.listENV COMPlus_DbgMiniDumpType 4ENV COMPlus_DbgMiniDumpName /dumps/%p-%e-%h-%t.dmpENV COMPlus_DbgEnableMiniDump 1ENTRYPOINT ["dotnet", "AspNetWebApi.dll"]這里有一個細節，為了能夠讓 Docker 中的 webapi 能夠訪問到，將 localhost 設置為 * ，修改 appsettings.json如下：
{ "urls": "http://*:5001", "Logging": { "LogLevel": { "Default": "Information", "Microsoft.AspNetCore": "Warning" } }, "AllowedHosts": "*"}有了這些基礎最后就是 docker build & docker run 啦。
[root@localhost data]# docker build -t aspnetapp .[+] Building 0.3s (9/9) FINISHED => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 447B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:6.0 0.3s => [1/4] FROM mcr.microsoft.com/dotnet/aspnet:6.0@sha256:a2a04325fdb2a871e964c89318921f82f6435b54 0.0s => [internal] load build context 0.0s => => transferring context: 860B 0.0s => CACHED [2/4] WORKDIR /app 0.0s => CACHED [3/4] COPY ./ ./ 0.0s => CACHED [4/4] RUN sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" /etc/apt/sources.list 0.0s => exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:be69203995c0e5423b2af913549e618d7ee8306fff3961118ff403b1359ae571 0.0s => => naming to docker.io/library/aspnetapp 0.0s[root@localhost data]# docker run -itd -p 5001:5001 --privileged -v /data2:/dumps --name aspnetcore_sample aspnetappca34c9274d998096f8562cbef3a43a7cbd9aa5ff2923e0f3e702b159e0b2f447[root@localhost data]# docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESca34c9274d99 aspnetapp "dotnet AspNetWebApi…" 20 seconds ago Exited (139) 9 seconds ago aspnetcore_sample[root@localhost data]# docker logs ca34c9274d99 ... at AspNetWebApi.Program.Test(System.String) at AspNetWebApi.Program.Test(System.String) at AspNetWebApi.Program.Test(System.String) at AspNetWebApi.Program.Test(System.String) at AspNetWebApi.Program+<>c.b__0_0() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task+<>c.<.cctor>b__272_0(System.Object) at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread, System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread) at System.Threading.Tasks.Task.ExecuteEntryUnsafe(System.Threading.Thread) at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart() at System.Threading.Thread.StartCallback()[createdump] Gathering state for process 1 dotnet[createdump] Crashing thread 0017 signal 6 (0006)[createdump] Writing full dump to file /dumps/1-dotnet-ca34c9274d99-1687746929.dmp[createdump] Written 261320704 bytes (63799 pages) to core file[createdump] Target process is alive[createdump] Dump successfully written[root@localhost data2]# cd /data2[root@localhost data2]# ls -lntotal 255288-rw-------. 1 0 0 261414912 Jun 26 10:35 1-dotnet-ca34c9274d99-1687746929.dmp 上面的腳本已經寫的非常清楚了，這里有幾個注意點提一下：
--privileged一定要加上特殊權限，否則生成 dump 的時候會提示無權限。
-v /data2:/dumps防止dump丟失，記得掛載到宿主機目錄 或者 共享容器 中。
2. 內存暴漲 dump 捕獲要想對 docker 中的 .NET 程序內存 進行監控，我一直都是極力推薦 procdump，目前最新的是版本是 1.5， github官網地址： https://github.com/Sysinternals/ProcDump-for-Linux 鑒于現在訪問 github 太慢，大家可以把 procdump_1.5-16239_amd64.deb下載到本地，為什么下載它，是因為容器中是 debain 系統。
下載好了之后放到項目中，使用默認代碼骨架：
public class Program { public static void Main(string[] args) { var builder = WebApplication.CreateBuilder(args); builder.Services.AddAuthorization(); var app = builder.Build(); app.UseAuthorization(); app.Run(); } }接下來就是寫 dockerfile 了，這里有一個細節，就是如何在 Docker 中開啟多進程，這里用 start.sh 腳本的方式開啟，參考代碼如下：
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS runtimeWORKDIR /appCOPY ./ ./# 1. 使用中科大鏡像源RUN sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" /etc/apt/sources.list# 2. 安裝 gdb & procdumpRUN apt-get update && apt-get install -y gdbRUN dpkg -i procdump.debRUN echo "#!/bin/bash \n\procdump -m 30 -w dotnet /dumps & \n\dotnet \$1 \n\" > ./start.shRUN chmod +x ./start.shENTRYPOINT ["./start.sh", "AspNetWebApi.dll"]有了這些設置后，接下來就是 publish 代碼用 docker 構建啦，為了方便演示，這里就用 前臺模式開啟了哈。
[root@localhost data]# docker build -t aspnetapp .[+] Building 11.5s (13/13) FINISHED [root@localhost data]# docker rm -f aspnetcore_sampleaspnetcore_sample[root@localhost data]# docker run -it --rm -p 5001:5001 --privileged -v /data2:/dumps --name aspnetcore_sample aspnetappProcDump v1.5 - Sysinternals process dump utilityCopyright (C) 2023 Microsoft Corporation. All rights reserved. Licensed under the MIT license.Mark Russinovich, Mario Hewardt, John Salem, Javid HabibiSysinternals - www.sysinternals.comMonitors one or more processes and writes a core dump file when the processes exceeds thespecified criteria.[02:57:34 - INFO]: Waiting for processes "dotnet" to launch[02:57:34 - INFO]: Press Ctrl-C to end monitoring without terminating the process(es).Process Name: dotnetCPU Threshold: n/aCommit Threshold: >=30 MBThread Threshold: n/aFile Descriptor Threshold: n/aSignal: n/aException monitor OffPolling Interval (ms): 1000Threshold (s): 10Number of Dumps: 1Output directory: /dumps[02:57:34 - INFO]: Starting monitor for process dotnet (9)info: Microsoft.Hosting.Lifetime[14] Now listening on: http://[::]:5001info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down.info: Microsoft.Hosting.Lifetime[0] Hosting environment: Productioninfo: Microsoft.Hosting.Lifetime[0] Content root path: /app/[02:57:35 - INFO]: Trigger: Commit usage:48MB on process ID: 9[createdump] Gathering state for process 9 dotnet[createdump] Writing full dump to file /dumps/dotnet_commit_2023-06-26_02:57:35.9[createdump] Written 254459904 bytes (62124 pages) to core file[createdump] Target process is alive[createdump] Dump successfully written[02:57:35 - INFO]: Core dump 0 generated: /dumps/dotnet_commit_2023-06-26_02:57:35.9[02:57:36 - INFO]: Stopping monitors for process: dotnet (9)[root@localhost data2]# ls -lhtotal 243M-rw-------. 1 root root 243M Jun 26 10:57 dotnet_commit_2023-06-26_02:57:35.9從腳本信息看，當內存到了 48MB的時候觸發的 dump 生成，也成功的進入了 /dumps目錄中，太棒了。
抓 cpu 爆高的dump最好的方式就是多抓幾個，比如說：當 CPU >20% 連續超過 5s 抓 2個dump，這種方式抓的dump很容易就能找到真兇，為了方便演示，讓兩個 cpu 直接打滿，參考代碼如下：
public static void Main(string[] args) { var builder = WebApplication.CreateBuilder(args); builder.Services.AddAuthorization(); var app = builder.Build(); app.UseAuthorization(); //3. cpu app.MapGet("/cpu", (HttpContext httpContext) => { Task.Factory.StartNew(() => { bool b = true; while (true) { b = !b; } }); Task.Factory.StartNew(() => { bool b = true; while (true) { b = !b; } }); return new WeatherForecast(); }); app.Run(); }接下來就是修改 dockerfile，因為我的虛擬機是 8 核心，如果兩個核心被打滿，那應該會占用大概 24% 的 cpu 利用率，所以腳本中就設置 20% 吧。
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS runtimeWORKDIR /appCOPY ./ ./# 1. 使用中科大鏡像源RUN sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" /etc/apt/sources.list# 2. 安裝 wgetRUN apt-get update && apt-get install -y gdbRUN dpkg -i procdump.debRUN echo "#!/bin/bash \n\procdump -c 20 -n 2 -s 5 -w dotnet /dumps & \n\dotnet \$1 \n\" > ./start.shRUN chmod +x ./start.shENTRYPOINT ["./start.sh", "AspNetWebApi.dll"]最后就是 docker 構建。
[root@localhost data]# docker build -t aspnetapp .[+] Building 0.4s (13/13) FINISHED[root@localhost data]# docker run -it --rm -p 5001:5001 --privileged -v /data2:/dumps --name aspnetcore_sample aspnetappProcDump v1.5 - Sysinternals process dump utilityCopyright (C) 2023 Microsoft Corporation. All rights reserved. Licensed under the MIT license.Mark Russinovich, Mario Hewardt, John Salem, Javid HabibiSysinternals - www.sysinternals.comMonitors one or more processes and writes a core dump file when the processes exceeds thespecified criteria.[03:35:56 - INFO]: Waiting for processes "dotnet" to launch[03:35:56 - INFO]: Press Ctrl-C to end monitoring without terminating the process(es).Process Name: dotnetCPU Threshold: >= 20%Commit Threshold: n/aThread Threshold: n/aFile Descriptor Threshold: n/aSignal: n/aException monitor OffPolling Interval (ms): 1000Threshold (s): 5Number of Dumps: 2Output directory: /dumps[03:35:56 - INFO]: Starting monitor for process dotnet (8)info: Microsoft.Hosting.Lifetime[14] Now listening on: http://[::]:5001info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down.info: Microsoft.Hosting.Lifetime[0] Hosting environment: Productioninfo: Microsoft.Hosting.Lifetime[0] Content root path: /app/看輸出是正在監控，接下來我們訪問下網址： http://192.168.17.129:5001/cpu，稍等片刻之后就會生成兩個dump 文件。
雖然Docker中的 .NET 程序占比較少，但把經驗總結出來還是很值得的，以后有人問怎么抓，可以把這篇文章直接丟過去啦！
關鍵詞：
版權與免責聲明：
1 本網注明“來源：×××”（非商業周刊網）的作品，均轉載自其它媒體，轉載目的在于傳遞更多信息，并不代表本網贊同其觀點和對其真實性負責，本網不承擔此類稿件侵權行為的連帶責任。
2 在本網的新聞頁面或BBS上進行跟帖或發表言論者，文責自負。
3 相關信息并未經過本網站證實，不對您構成任何投資建議，據此操作，風險自擔。
4 如涉及作品內容、版權等其它問題，請在30日內同本網聯系。
