Enterprise-grade Gitea container with FIPS 140-2 compliance, providing a secure, self-hosted Git service with integrated CI/CD capabilities. Features enhanced security controls, STIG hardening, and comprehensive audit logging for regulated environments.
Core capabilities and strengths of this container
Typical scenarios where this container excels
Download the container image from the registry
docker pull clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:latestdocker pull clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:1.20Run the container with basic configuration
docker run -d --name gitea-fips \
-p 3000:3000 \
-v gitea-data:/data \
clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:latestDeploy with production security settings
docker run -d --name gitea-fips-prod \
--read-only \
--security-opt=no-new-privileges \
--user 1000:1000 \
-v gitea-data:/data \
-v gitea-config:/etc/gitea \
-p 3000:3000 \
-p 22:22 \
clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:latestMount local directory for persistent data
docker run -d \
-v $(pwd)/gitea-data:/data \
-v $(pwd)/gitea-config:/etc/gitea \
clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:latestRun with custom port mappings
docker run -d \
-p 8080:3000 \
-p 2222:22 \
clnstrt-images.cleanstart.com/$ORGANIZATION/gitea-fips:latestConfiguration options available through environment variables
/data/gitea/dataGiteaprodRecommended security configurations and practices
Recommended security context for Kubernetes deployments
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
fsGroup: 1000
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
seccompProfile:
type: RuntimeDefaultEssential links and resources for further information