step-cli

Free

FIPS AvailableSecurity Hardened

Description

The CleanStart Step-Cli image provides a production-ready, security-hardened container optimized for enterprise environments. Built on a minimal base OS with comprehensive security hardening, this image delivers reliable application execution with advanced security features.

Key Features

Core capabilities and strengths of this runtime container

Production-ready container deployment
Enterprise-grade security hardening
Comprehensive monitoring and logging
Multi-architecture support

Common Use Cases

Typical scenarios where this runtime container excels

Production application deployment
Microservices architecture implementation
Development and testing environments
Enterprise workload containerization

Pull Commands

Download the runtime container images

docker pull <Registry URL>/cleanstartos/step-cli:latest

docker pull <Registry URL>/cleanstartos/step-cli:latest-dev

Interactive Development

Start interactive session for development

bash

docker run -d --name step-cli-prod \\
  --read-only \\
  --security-opt=no-new-privileges \\
  --user 1000:1000 \\
  <Registry URL>/cleanstartos/step-cli:latest

Run Hello World

Execute a simple Hello World program

bash

docker run -it --name step-cli-test <Registry URL>/cleanstartos/step-cli:latest-dev

Mount Workspace

Run container with local workspace mounted

bash

docker run --rm -v $(pwd):/app -w /app <Registry URL>/cleanstartos/step-cli:latest-dev python --version

Application Server

Run application with port forwarding

bash

docker run -d --name step-cli-app \
  -p 8000:8000 \
  -v $(pwd):/app \
  -w /app \
  <Registry URL>/cleanstartos/step-cli:latest

Environment Variables

Configuration options available through environment variables

PATH: System PATH configuration; /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Security Best Practices

Recommended security configurations and practices

Use specific image tags for production (avoid latest)
Configure resource limits: memory and CPU constraints
Enable read-only root filesystem when possible
Run containers with non-root user (--user 1000:1000)
Use --security-opt=no-new-privileges flag
Regularly update container images for security patches
Implement proper network segmentation
Monitor container metrics for anomalies

Kubernetes Security Context

Recommended security context for Kubernetes deployments

yaml

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ['ALL']