<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VS Code on jqknono Blogs</title><link>https://blog.jqknono.com/tags/vs-code/</link><description>Recent content in VS Code on jqknono Blogs</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>https://blog.jqknono.com (jqknono)</managingEditor><webMaster>https://blog.jqknono.com (jqknono)</webMaster><lastBuildDate>Fri, 03 Apr 2026 10:30:00 +0800</lastBuildDate><atom:link href="https://blog.jqknono.com/tags/vs-code/index.xml" rel="self" type="application/rss+xml"/><item><title>VS Code Dev Container High IO Usage: executeInWSL Configuration Details and Root Cause Analysis</title><link>https://blog.jqknono.com/blog/2026/04/03/vscode-dev-container-io-performance/</link><pubDate>Fri, 03 Apr 2026 10:30:00 +0800</pubDate><author>https://blog.jqknono.com (jqknono)</author><guid>https://blog.jqknono.com/blog/2026/04/03/vscode-dev-container-io-performance/</guid><description>Documenting the complete troubleshooting process for the high IO usage issue caused by VS Code Dev Container extensions on Windows, from phenomenon identification to root cause analysis, ultimately resolving the Docker CLI cross-boundary communication bottleneck with dev.containers.executeInWSL as the core solution.</description></item></channel></rss>