Mojo Dev Container for standard library development

[benz0li]

Multi-arch (linux/amd64, linux/arm64/v8) Mojo Dev Container.
🔥 All prerequisites installed for Mojo standard library development.

Parent image: glcr.b-data.ch/mojo/base:nightly

Features

• Git: A distributed version-control system for tracking changes in source code.
• Git LFS: A Git extension for versioning large files.
• LLVM (optional, installed): A collection of modular and reusable compiler and toolchain technologies.
• Mojo (nightly): A programming language for AI developers.
• Pandoc: A universal markup converter.
• Python: An interpreted, object-oriented, high-level programming language with dynamic semantics.
• Zsh: A shell designed for interactive use, although it is also a powerful scripting language.

Pre-installed extensions

• Black Formatter
• Docker
• EditorConfig for VS Code
• Git Graph
• GitHub Pull Requests and Issues
• GitLens — Git supercharged
  ℹ️ Pinned to version 11.7.0 due to unsolicited AI content
• hadolint
• Jupyter
• markdownlint
• Mojo 🔥 (nightly)
• Python
• Resource Monitor
• ShellCheck
• YAML

ℹ️ For further information, see https://github.com/benz0li/mojo-dev-container

---

What makes this Dev Container different:

1. Multi-arch: linux/amd64, linux/arm64/v8
   ℹ️ Runs on Apple M series using Docker Desktop¹.
2. Base image: Debian instead of Ubuntu
3. Just Python – no Conda / Mamba

---

Cross reference:

• [docs] Add section 'Dev Container' to the Mojo stdlib docs #2664

Footnotes

1. Please be aware of https://github.com/benz0li/mojo-dev-container/issues/1 ↩

[benz0li]

Usage

The Mojo Dev Container behaves in a unique way:

1. Default mount:
   • source: empty directory
   • target: /home/vscode
   • type: volume
2. Codespace only mount:
   • source: root of this repository
   • target: /workspaces
   • type: misc
3. Default path: /home/vscode/projects/modularml/mojo
   • Repository: https://github.com/modularml/mojo.git
   • Branch: nightly
4. Default user: vscode
   • uid: 1000 (auto-assigned)
   • gid: 1000 (auto-assigned)
5. Lifecycle scripts:
   • onCreateCommand: home directory setup
   • postStartCommand: Codespace only: Silently remove all unused images and all build cache
   • postAttachCommand: Codespace only: Check for Dev Container updates

To disable the postStartCommand or postAttachCommand, comment out line 8 in ~/.local/bin/dockerSystemPrune.sh or ~/.local/bin/checkForUpdates.sh.

Codespace

1. Click the <> Code button, then click the Codespaces tab.
   A message is displayed at the bottom of the dialog telling you who will pay for the codespace.
2. Create your codespace after configuring advanced options:
   • Configure advanced options
     To configure advanced options for your codespace, such as a different machine type or a particular devcontainer.json file:
     • At the top right of the Codespaces tab, select ... and click New with options....
     • On the options page for your codespace, choose your preferred options from the dropdown menus.
     • Click Create codespace.

– Creating a codespace for a repository - GitHub Docs

Local/'Remote SSH'

Use the Dev Containers: Reopen in Container command from the Command Palette (F1, ⇧⌘P (Windows, Linux Ctrl+Shift+P))

ℹ️ For further information, see Developing inside a Container using Visual Studio Code Remote Development.

Persistence

Data in the following locations is persisted:

1. The user's home directory (/home/vscode)¹
2. The Dev Container's workspace (/workspaces)

This is accomplished via a volume (or loop device on Codespaces) and is preconfigured.

Codespaces: A 'Full Rebuild Container' resets the home directory! ℹ️ This is never necessary unless you want exactly that.

Footnotes

1. Alternatively for the root user (/root). Use with Docker/Podman in rootless mode. ↩