envbuilder is a CLI tool written in Go that builds and runs Dev Containers (as defined by devcontainer.json) inside Docker containers, using a forked version of Kaniko for image building. In production, it clones a Git repository, locates a devcontainer.json or Dockerfile, compiles a Dockerfile with requested features, builds the image via Kaniko (with layer caching), and then executes lifecycle scripts (onCreate, postCreate, etc.) before running an init command as a specified user. It is designed to integrate with Coder workspaces for log forwarding but can operate standalone. The architecture is a single binary with modular components: options parsing (options/), Git operations (git/), devcontainer spec handling (devcontainer/), Kaniko build orchestration (envbuilder.go), and logging (log/). It relies on system calls for user switching (setuid), execution (exec), and filesystem mounts. External dependencies include Git, Docker daemon, and the Kaniko fork. The tool supports extensive configuration via CLI flags and environment variables, with legacy variable support. Key entry points are cmd/envbuilder/main.go (CLI) and envbuilder.go (Run function). The primary data flow is: input options -> clone repo -> parse devcontainer -> compile Dockerfile -> Kaniko build -> execute lifecycle scripts -> setuid -> exec init. The tool also includes a cache probe mode for checking layer availability without full build.
This repository is a static documentation repository that serves as a reference manual for Git commands. It contains a comprehensive README.md file in Chinese that covers a wide range of Git operations, including configuration, branching, merging, rebasing, and advanced techniques like submodules and worktree management. The repository does not contain any executable code or scripts; it is purely a reference guide for developers to learn and use Git effectively. The architecture is simple: a single Markdown file accompanied by illustrative images and GIFs stored in a media directory. There are no external dependencies, and the content is self-contained. The repository is actively maintained, with recent commits ensuring the content remains relevant to current Git practices.