vikshan/bunode repository overview

⁠DevContainer Configurations

This repository contains reusable DevContainer configurations for different development environments. All images now default to a customized Zsh + Oh My Zsh interactive shell experience.

⁠Available Images

⁠🎯 Choose Your Image

Need Bun runtime?
├─ Yes → Need Node.js?
│  ├─ Yes → Need Ubuntu base?
│  │  ├─ Yes → ubun-tu-node
│  │  └─ No  → bunode
│  └─ No  → Need Ubuntu base?
│     ├─ Yes → ubun-tu
│     └─ No  → bun
└─ No  → ubuntu

⁠📦 Quick Start

docker pull ghcr.io/iamvikshan/devcontainer/bun:latest
docker pull ghcr.io/iamvikshan/devcontainer/bunode:latest
docker pull ghcr.io/iamvikshan/devcontainer/ubun-tu:latest
docker pull ghcr.io/iamvikshan/devcontainer/ubun-tu-node:latest
docker pull ghcr.io/iamvikshan/devcontainer/agents:latest
docker pull ghcr.io/iamvikshan/devcontainer/ubuntu:latest

⁠Usage

⁠DevContainer Configuration

Add your chosen image to .devcontainer/devcontainer.json:

{
  "name": "My Bun Project",
  "image": "ghcr.io/iamvikshan/devcontainer/bun:latest",
  "customizations": {
    "vscode": {
      "extensions": ["oven.bun-vscode", "esbenp.prettier-vscode"],
      "settings": {
        "terminal.integrated.defaultProfile.linux": "zsh"
      }
    }
  },
  "postCreateCommand": "bun install"
}

⁠Docker Run

# Interactive development
docker run -it --rm \
  -v $(pwd):/workspace \
  -w /workspace \
  ghcr.io/iamvikshan/devcontainer/bun:latest \
  zsh

# Run commands directly
docker run --rm \
  -v $(pwd):/workspace \
  -w /workspace \
  ghcr.io/iamvikshan/devcontainer/bun:latest \
  bun install

⁠Docker Compose

version: '3.8'
services:
  dev:
    image: ghcr.io/iamvikshan/devcontainer/bun:latest
    volumes:
      - .:/workspace
    working_dir: /workspace
    command: sleep infinity

⁠📚 Documentation

For comprehensive setup instructions and detailed information:

• Setup Guide⁠ - Complete setup instructions for all images
• Image Variants⁠ - Detailed comparison and use cases
• Build Commands⁠ - Building and testing images locally
• Current Versions⁠ - Latest versions, sizes, and changelogs

⁠Image Details

⁠What's Included

All images include:

• Git - Version control
• SSH client - Secure connections
• curl - HTTP requests
• btop - System resource monitor
• Basic development utilities

⁠Alpine-based Images (bun, bunode)

• Bun - Fast TypeScript and JavaScript runtime
• Node.js (bunode only)
• npm (bunode only)

⁠Ubuntu-based Images (ubun-tu, ubun-tu-node)

• Bun - Installed via script
• Node.js (ubun-tu-node only)
• npm (ubun-tu-node only)
• sudo - Administrative access
• Ubuntu package manager (apt)

⁠Ubuntu tools-only Image (ubuntu)

• jq - JSON processing utility
• No Bun, Node.js, or npm - Purpose-built tools-only variant
• sudo - Administrative access
• Ubuntu package manager (apt)

⁠Building Locally

Want to build or customize these images? See docs/BUILD_COMMANDS.md⁠ for complete instructions.

⁠Automated Updates

This repository includes automated systems to keep the devcontainers up to date:

⁠🔄 Smart Release System

• Independent container versioning - each container has its own semantic version
• Semantic commit analysis - automatic version bumping based on conventional commits
• Push-triggered releases - releases created when changes are pushed to main
• Weekly scheduled releases - every Sunday at 2 AM UTC for base image updates

⁠🔍 Base Image Monitoring

• Weekly checks for updates to base images (oven/bun, ubuntu)
• Granular rebuilds - only affected containers are rebuilt
• Automatic issue creation when builds fail
• Tool version extraction during build process

⁠📦 Multi-Registry Support

• GitHub Container Registry (ghcr.io) - primary registry
• GitLab Container Registry (registry.gitlab.com) - mirror
• Docker Hub (docker.io) - public access
• GitHub Actions updated daily

⁠Image Management

Monitor and manage the images:

# Check for base image updates
bun run check-updates

# Analyze image sizes across all registries
bun run analyze-sizes

# Update documentation with current sizes
bun run sync-sizes

⁠Contributing

1. Fork⁠ the repository
2. Create a feature branch
3. Submit a pull request⁠