OpenParable
Skip to content
← Back to skills

Crosvm Dev Container

DevOps & Security
crosvm-dev-container

Crosvm Dev Container is an Agent Skill for devops & security published in the google/crosvm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Skill to assist with using the `dev_container` tool for running builds, tests, and other tools in a consistent containerized environment.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/google/crosvm/blob/HEAD/.agents/skills/crosvm_dev_container/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/crosvm-dev-container, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Crosvm Dev Container (tools/dev_container)

The tools/dev_container script is a wrapper used to run commands inside the official crosvm development container. This ensures a consistent environment with all necessary dependencies installed (such as compilers, libraries, and system tools).

It uses Podman by default, but can fall back to or be forced to use Docker.

Basic Usage

To run any command inside the dev container, prefix it with tools/dev_container:

tools/dev_container <command>

Common Examples:

  • Run cargo check: 
    tools/dev_container cargo check
  • Run presubmit checks: 
    tools/dev_container ./tools/presubmit quick
  • Run formatting: 
    tools/dev_container ./tools/fmt

Key Options

  • --use-docker: Force the script to use Docker instead of Podman.
  • --pull: Pull the latest version of the container image from the registry before running the command.
  • --stop: Stop the currently running container instance.
  • --clean: Clean the container state (useful if the container gets into a bad state).
  • --no-interactive: Run in non-interactive mode (useful for scripts or CI).