bascule-oss/images/README.md
Tyler King e7fc9fa5e1 feat: structured logging, tracing spans, comprehensive documentation
Observability:
  Structured JSON logging via BASCULE_LOG_FORMAT=json
  Tracing spans on auth (method, principal, peer)
  Tracing spans on session lifecycle (id, principal, backend, source_ip)
  Tracing spans on exec requests (session_id, command)
  Config: [telemetry] and [metrics] sections (OTel export planned)

Documentation (8 files, 489 lines):
  docs/quickstart.md — three-path getting started
  docs/configuration.md — full config reference with examples
  docs/authentication.md — all auth modes with setup guides
  docs/architecture.md — backends, traits, extension model, security
  docs/observability.md — logging, tracing, metrics
  docs/comparison.md — vs Teleport, Boundary, StrongDM
  images/README.md — curated image catalog
  README.md — features, comparison, quickstart, extension example

1557 lines Rust, 489 lines docs, 0 substrate deps.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-04 23:45:03 -04:00

1,009 B

Bascule Shell Images

Curated container images for right-sized operator environments.

Image Contents Approx. Size
bascule-shell:minimal bash, coreutils, curl, jq, ssh ~50MB
bascule-shell:k8s-ops + kubectl, helm ~120MB
bascule-shell:net-ops + nmap, dig, traceroute, tcpdump, nft ~90MB
bascule-shell:dev + git, make, gcc, python3, vim ~250MB

Building

docker build -t bascule-shell:minimal images/minimal/
docker build -t bascule-shell:k8s-ops images/k8s-ops/
docker build -t bascule-shell:net-ops images/net-ops/
docker build -t bascule-shell:dev images/dev/

Right-Sizing

Choose the smallest image that contains the tools your operators need. If it's not in the image, the operator can't use it — the container IS the access boundary.

Custom Images

Build your own image from any base:

FROM bascule-shell:k8s-ops
USER root
RUN microdnf install -y your-custom-tool
USER operator