Choosing the Right Image¶

Use this guide to select the best DevOps image for your needs.

Decision Tree¶

flowchart TD
    START[Which image<br/>should I use?]

    START --> Q1{Working with<br/>multiple clouds?}

    Q1 -->|Yes| ALL[✅ Use all-devops<br/>✓ AWS + GCP tools<br/>✓ All features<br/>⚠️ Larger size ~3.2GB]

    Q1 -->|No| Q2{Which cloud<br/>provider?}

    Q2 -->|AWS| AWS_Q{Need AWS<br/>Session Manager?}
    Q2 -->|GCP| GCP[✅ Use gcp-devops<br/>✓ gcloud tools<br/>✓ GKE ready<br/>✓ Smaller ~2.9GB]
    Q2 -->|Neither/Local| BASE_Q{Need cloud<br/>CLI later?}

    AWS_Q -->|Yes| AWS[✅ Use aws-devops<br/>✓ AWS CLI v2<br/>✓ Session Manager<br/>✓ CloudFormation tools<br/>✓ ~2.8GB]
    AWS_Q -->|No| BASE_Q

    BASE_Q -->|Maybe| ALL
    BASE_Q -->|No| CONSIDER[Consider building<br/>custom base image<br/>without cloud tools]

    ALL --> SIZE_Q{Concerned about<br/>image size?}
    AWS --> SIZE_Q
    GCP --> SIZE_Q

    SIZE_Q -->|Yes| OPT[See Build Images ><br/>Optimization Guide]
    SIZE_Q -->|No| DONE[🎯 You're all set!<br/>See Use Images guide]

    style START fill:#4A90E2,color:#fff
    style ALL fill:#FF6B6B,color:#fff
    style AWS fill:#FF9F43,color:#fff
    style GCP fill:#5F8D4E,color:#fff
    style DONE fill:#48C774,color:#fff

Quick Comparison¶

Use Case Scenarios¶

Solo Developer - Local Development¶

Recommendation: Start with all-devops

• ✅ Maximum flexibility for experimentation
• ✅ Try both AWS and GCP without switching images
• ✅ All AI CLI tools for productivity
• ⚠️ Slightly larger, but comprehensive

docker pull ghcr.io/jinalshah/devops/images/all-devops:latest

Team - Standardized AWS Environment¶

Recommendation: aws-devops

• ✅ Smaller image for faster CI/CD pulls
• ✅ AWS-specific tools (Session Manager for EC2)
• ✅ No unnecessary GCP tools
• ✅ Team consistency

docker pull ghcr.io/jinalshah/devops/images/aws-devops:latest

Team - Google Cloud Platform¶

Recommendation: gcp-devops

• ✅ GCP-optimized with gcloud
• ✅ GCR authentication built-in
• ✅ Smaller than all-devops
• ✅ GKE-ready

docker pull ghcr.io/jinalshah/devops/images/gcp-devops:latest

CI/CD Pipeline - Multi-Cloud¶

Recommendation: all-devops with version pinning

• ✅ One image for all deployment targets
• ✅ Consistent tooling across pipelines
• ✅ Version pinning for reproducibility
• 🎯 Use immutable tags

docker pull ghcr.io/jinalshah/devops/images/all-devops:1.0.abc1234

Security-Conscious Team¶

Recommendation: Start with aws-devops or gcp-devops, scan with Trivy

• ✅ Smaller attack surface (fewer tools)
• ✅ Trivy included for vulnerability scanning
• ✅ Pin specific versions in production
• 🔒 Regular security updates

# Pull and scan
docker pull ghcr.io/jinalshah/devops/images/aws-devops:latest
docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  ghcr.io/jinalshah/devops/images/aws-devops:latest \
  trivy image ghcr.io/jinalshah/devops/images/aws-devops:latest

Size vs Features Trade-off¶

What's in Each Image?¶

pie title all-devops Size Breakdown (~3.2GB)
    "Rocky Linux Base" : 500
    "System Packages" : 800
    "Python + Packages" : 600
    "Cloud CLIs (AWS + GCP)" : 900
    "IaC Tools" : 300
    "Other Tools" : 100

Size Optimization Strategies¶

Feature Comparison Matrix¶

Infrastructure as Code Tools¶

Kubernetes Tools¶

Cloud Provider Tools¶

AI CLI Tools¶

Configuration Management¶

Still Not Sure?¶

Registry Choice¶

All images are available in three registries:

ghcr.io/jinalshah/devops/images/{image-name}:latest

registry.gitlab.com/jinal-shah/devops/images/{image-name}:latest

js01/{image-name}:latest

Next Steps¶

Once you've chosen your image:

1. Get Started: Follow the Quick Start Guide
2. Pull the Image: See Use Images for pull commands
3. Set Up Authentication: Configure credentials and volume mounts
4. Explore Workflows: Check out real-world examples
5. Customize: Learn how to build custom images

Quick Links:

• Architecture Overview
• Tool Basics
• Troubleshooting