rabbitmq-cluster-operator
Secure by Design, Built for Speed, Hardened Container Images on a minimal base CleanStart OS.
10K+
The CleanStart Rabbitmq-Cluster-Operator 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.
š Base Foundation: Production-ready container from cleanstart.
Image Path: cleanstart/rabbitmq-cluster-operator
Registry: cleanstart Registry
Download the container image from the registry
docker pull cleanstart/rabbitmq-cluster-operator:latest
docker pull cleanstart/rabbitmq-cluster-operator:latest-dev
Note: The operator will always print "unable to find operator namespace" when run outside Kubernetes ā this is expected. To fully exercise the image, deploy it into a Kubernetes cluster.
Run the container with basic configuration
docker run -it --name rabbitmq-cluster-operator \
cleanstart/rabbitmq-cluster-operator:latest
Deploy with production security settings
docker run -d --name rabbitmq-cluster-operator-prod \
--security-opt=no-new-privileges \
--user 1000:1000 \
--restart unless-stopped \
cleanstart/rabbitmq-cluster-operator:latest
Volume Mount Mount local directory for persistent data
docker run -v /app:/app \
--name rabbitmq-cluster-operator \
cleanstart/rabbitmq-cluster-operator:latest
Port Forwarding Run with custom port mappings
docker run -p 9782:9782 \
--name rabbitmq-cluster-operator \
cleanstart/rabbitmq-cluster-operator:latest
Recommended security context for Kubernetes deployments
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsUser: 1000
runAsGroup: 1000
Essential links and resources for further information
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.
Content type
Image
Digest
sha256:bc856d5bcā¦
Size
49.8 MB
Last updated
about 21 hours ago
docker pull cleanstart/rabbitmq-cluster-operator:2.22.1-arm64