devops.md

Bounty Service - DevOps Challenge

Overview

Welcome to the Bounty Service! This is a multi-level challenge that will test your DevOps and debugging skills. Your goal is to retrieve bounty secrets from each level by fixing various configuration and infrastructure issues.

Getting Started

Quick Start (Recommended)

# Pull the image
docker pull rootlyio/bounty-service:latest

# Run the container
docker run -d -p 8080:8080 --name bounty-app rootlyio/bounty-service:latest

# Test the service
curl http://localhost:8080/

Build Locally (Alternative)

# Build the image
docker build -t bounty-service .

# Run the container
docker run -d -p 8080:8080 --name bounty-app bounty-service

# Test the service
curl http://localhost:8080/

Using Docker Compose

# Start all services
docker-compose up -d

# Check status
docker-compose ps

# View logs
docker-compose logs -f app

The Challenge

Your objective is to retrieve bounty secrets from multiple levels. Each level presents unique challenges that build upon previous ones.

Start by accessing:

curl http://localhost:8080/bounty/level1

Progress through the levels sequentially. Each successful level will provide hints for the next challenge.

Available Endpoints

• GET / - Service information
• GET /health - Health check with diagnostics
• GET /bounty/level1 - First challenge
• GET /bounty/level2 - Second challenge (unlock by completing level 1)
• GET /bounty/level3 - Third challenge (unlock by completing level 2)
• Additional endpoints may exist...

Useful Commands

# Check container logs
docker logs bounty-app

# Execute commands inside container
docker exec bounty-app <command>

# Access container shell
docker exec -it bounty-app /bin/bash

# Database operations
docker exec bounty-app bundle exec rake -T

# Restart services
docker-compose restart

Success Criteria

Successfully retrieve bounty secrets from all levels. Each bounty follows the format: rootly{...}

Tips

• The /health endpoint provides valuable diagnostic information
• Error messages often contain helpful hints
• Some solutions require examining the application code
• Configuration can come from multiple sources
• Not everything is documented

Requirements

• Docker
• curl or any HTTP client
• Problem-solving skills
• Persistence

Good luck!