write in front

This blog is just a simple record: I tossed the process of Microsoft’s official Dev Containers extension in Trae CN.Let’s talk about the conclusion first: Tossing around and discovering TRAE CN currently (June 2026)Not supported yet dev containers. So this article will not give any ‘perfect solution’, and only leave an introduction in the end – the next step I plan to try another path:Host Go + Container Run + Docker Extension Assist, if you run through, write a separate article to share.

project background: I am now writing with trae cn on ubuntu 26.04 go-gin-learning((https://github.com/shuijingwan/go-gin-learning), a small project of Go + Gin.

Two blogs that have been completed before(all have already been posted):

1. ‘Build the basic environment based on Docker Compose + Go 1.26.4 in Ubuntu 26.04’
   https://www.shuijingwanwq.com/en/2026/06/03/15642/
   This article mainly fixes the Docker environment, container startup, MySQL/Redis network, etc.
2. GO + GIN RESTful API: From Environment Build (WSL/Docker/VS Code) to Git Commit and GitHub Hosting
   https://www.shuijingwanwq.com/en/2026/04/03/11106/
   This is in Windows WSL + Docker + VS Code A complete set of processes that have been successfully run through. Now I want to ubuntu + docker + trae cn Implement the same thing again.

So this article is actually a small episode in the middle: I want to try whether I can also use dev containers to ‘moving’ the entire editor into the container in the trae cn, and it turns out that… it is not for the time being.

Why do you want to try dev containers?

Students who have used VS Code should know that the function of Dev Containers is really delicious: you can stuff the entire development environment (including the Go version, toolchain, extension, terminal) into a Docker container. When teamwork or machine change, open the project and click ‘Reopen in container’ to start working directly without installing a bunch of things.

I have used it very well on Windows + WSL + VS Code before (that’s what I wrote in the second blog). So after switching to ubuntu + trae cn, I naturally want to re-enact this experience. So there is the following tossing process.

2. Record of the process of stepping on the pit

2.1 First match the expansion market address

The default expansion market address of TRAE CN isEmpty, you have to fill it yourself. I’m in the settings application.extensionmarketURL Changed to https://marketplace.visualstudio.com/.

[截图 3：修改 application.extensionMarketUrl 设置]

2.2 Install the official Dev Containers extension

After the address is configured, you can find the official Microsoft ms-vscode-remote.remote-containers out. Click Install.

[截图 4：官方 Dev Containers 扩展的详情页]

After installing it, the status bar says ‘Users have disabled this extension globally’. Huh? I didn’t do anything…

[截图 5：扩展显示“用户已全局禁用此扩展”及右键菜单]

2.3 Try various ‘enabled’ poses

• Click on the extension details page ‘Enable (Workspace)’ → No response.
• with command panel Extensions: Enable Extension Select dev containers → still no response.
• Even forcibly add 'extensions.enabled' Configuration → still invalid.

[截图 7：工作区设置中添加强制启用配置]

2.4 Try another market source?

I replaced the market address with https://open-vsx.org/, restart trae cn and search for dev containers – the result is found Open-VSX can’t find the official Microsoft extension at all, only a community version called ‘Artizo dev containers for trae’ came out.

[截图 8：社区版 Artizo Dev Containers for Trae 扩展（仅展示，我没敢装）]

To be honest, I am a little worried about the community version, and I don’t dare to pretend casually.

2.5 Finally try to install VSIX offline

I think, since it is not online, then download the VSIX file manually. Take one out of the VS Code market ms-vscode-remote.remote-containers-0.459.1.vsix, and then use it in trae cn ‘Installation from VSIX’ guide in.

[截图 9：从本地 VSIX 文件安装扩展的文件选择对话框]

The installation process looks normal, but after installing… still ‘Users have been disabled globally’. This means that the problem is not in the download or installation link, but the extension itself is not compatible with the activation mechanism of TRAE CN.

2.6 Smooth Docker Extension

Although Dev Containers is useless, I do it MS-AzureTools.vscode-docker(Container tools) are installed, and this can still be used later.

[截图 1：Trae CN 扩展商店中 Docker 扩展的安装界面]

In addition, the container in the Docker sidebar is also running normally.

2.7 Take a look at the official forum

Finally, I went to the official forum of TRAE and searched, and someone asked:[Feedback] Dev Containers extension cannot be used. The official reply is very clear:Dev Containers is not currently supported.

Well, give up.

3. The conclusion is that it is really not supported at present

Summarize the results of this attempt:

• The official extension is installed, but it always shows that ‘the user has been disabled globally’ and cannot be activated.
• There is no official version in the open-vsx market at all, there is only one community version (I didn’t install it).
• Manual VSIX installation cannot be saved, just like it is disabled.
• The official forum confirmed: not supported.

So, if you also want to reproduce the ‘one-click container’ development experience in VS Code in Trae CN,Don’t bother for now.

4. What are you going to do next?

Although dev containers can’t work, the development still has to continue. I’m going to change my mind and try it ‘Host Go + Container Run + Docker Extension Assistant’ This mixing mode. The general idea is:

• The host machine installs a Go SDK, so that the code completion of the TRAE CN can work normally.
• The container continues to run and test, and directly operate the terminals within the container through the ‘Attach shell’ extended by the Docker.
• The Git operation uses the source code management panel that comes with the Trae CN (the actual tune is the Git of the host), and the code is automatically synchronized through the Volumes mount.

This plan has not officially run, just my next plan. If I can run smoothly, I will write a separate blog to share the specific configuration and usage.