chef/bento

Packer templates for building minimal Vagrant baseboxes for multiple platforms

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 15th, 2026
Created on March 7th, 2012
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 1,116
Total Stargazers: 4,448 (+0)
Total Subscribers: 187 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.1 hours
Mean response time: 42.2 days
90th percentile: 123.9 days
Tracked items: 51

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 384 days
Stale 30+ days: 15
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Status: Untriaged (42)
  • Triage: Feature Request (2)
  • Triage: Confirmed (1)
  • Type: Design Proposal (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Bento is a Packer template project that builds minimal Vagrant base boxes for multiple platforms and virtualization providers.

The project solves the problem of creating consistent, reproducible Vagrant base boxes across different operating systems and hypervisors. It encapsulates Packer templates that automate the box-building process, handling the complexity of configuring each platform's specific requirements. A subset of built templates are published to Vagrant Cloud under the bento organization and serve as default boxes for kitchen-vagrant, a testing framework integration.

Developers should choose Bento if they need to build custom Vagrant boxes or want to understand how minimal base boxes are constructed for multiple platforms. The project suits teams using Vagrant for local development environments or infrastructure testing who require boxes beyond the published defaults. The tool supports a wide range of providers including VirtualBox, VMware Fusion, VMware Workstation, Parallels Desktop Pro, UTM, qemu, and Hyper-V, though qemu and Hyper-V support is marked as experimental. The bento executable provides a command-line interface for building boxes with options to specify CPU and memory allocation, use custom variable files, select specific providers, and control build behavior through flags like dry-run and debug.

The project maintains active engagement with its templates, regularly updating them to support new CPU architectures and virtualization features. Development includes careful attention to compatibility requirements, such as specifying minimum versions for Vagrant and VirtualBox needed for particular functionality. The tool is distributed as a Ruby gem, indicating ongoing maintenance of its packaging and installation infrastructure. Documentation covers both using published boxes and building custom ones, with explicit guidance on directory structure and command execution to ensure predictable build outputs.