cleanstart/step-cli repository overview

Container Documentation for Step-Cli

Step CLI is a command-line interface tool for automated certificate management, PKI operations, and OAuth workflows. This container provides a secure, enterprise-ready environment for automated certificate lifecycle management, identity provisioning, and cryptographic operations in containerized deployments.

📌 Base Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments from Cleanstart Registry.

Key Features Core capabilities and strengths of this container

• Automated X.509 certificate management
• OAuth OIDC automation and workflows
• Zero-trust security architecture support
• Integrated PKI operations and tooling

Common Use Cases Typical scenarios where this container excels

• Automated certificate lifecycle management
• PKI infrastructure automation
• OAuth/OIDC integration workflows
• Zero-trust security implementations

Pull Latest Image Download the container image from the registry

docker pull cleanstart/step-cli:latest

docker pull cleanstart/step-cli:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name step-cli-test cleanstart/step-cli:latest-dev

Production Deployment Deploy with production security settings

docker run -d --name step-cli-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  cleanstart/step-cli:latest

Volume Mount Mount local directory for persistent data

docker run -v $(pwd)/certs:/home/step/certs cleanstart/step-cli:latest

Port Forwarding Run with custom port mappings

docker run -p 9000:9000 cleanstart/step-cli:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use specific image tags for production deployments
• Implement proper certificate storage security
• Enable read-only filesystem access
• Run as non-root user
• Secure sensitive environment variables
• Regular security updates and patches
• Implement proper access controls
• Monitor certificate lifecycle events

Kubernetes Security Context Recommended security context for Kubernetes deployments

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

⁠Documentation Resources

Essential links and resources for further information

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.