VS Codium

VS Codium attaches to a workbench over the SSH attach point. (The Microsoft Dev Containers extension isn’t on Open VSX, so the SSH route is the way - and it works just as well.)

Note

acme is just a sample workbench name - it’s whatever you passed to monoceros init. Substitute your own throughout.

Prerequisites: Docker is running and the workbench is applied and up (monoceros apply acme, check with monoceros status acme).

Connect

1. Install Open Remote - SSH (publisher jeanp413) from the Extensions view - it’s on Open VSX, Codium’s default marketplace. Do not install Microsoft’s “Remote - SSH”; it isn’t available here.

2. Click Open a Remote Window (the >< button at the bottom-left of the window).

3. Choose Connect to Host… and enter monoceros-acme.

4. In the new window, run File -> Open Workspace from File… and select /workspaces/acme/acme.code-workspace.

The host monoceros-acme and its key are written by monoceros apply - nothing to set up by hand.

Tip

Or open it in one command:

monoceros open acme codium

Or attach right after bringing the container up - both work:

monoceros apply acme --open codium
monoceros start acme --open codium

Windows / WSL

Works the same. monoceros apply runs in WSL but also writes the Windows ~/.ssh/config entry and key, so monoceros open acme codium and Remote-SSH: Connect to Host… resolve monoceros-acme from Windows with nothing to set up. You need Docker Desktop (provides docker.exe) and the Windows OpenSSH client (bundled since Windows 10).

Your setup persists

Installed extensions and user settings live in named Docker volumes (~/.vscodium-server), so they survive a monoceros apply rebuild. monoceros remove acme deletes them along with the container.

Trouble?

See the IDE FAQ.