 |
VOOZH | about |
|
VOOZH | about |
The default storage for ServiceControl instances.
100K+
The particular/servicecontrol-ravendb image is part of the Particular Service Platform, which includes the following images:
| Image Name | Documentation | Purpose |
|---|---|---|
particular/servicecontrol | Instance Documentation Container Documentation | The primary/error instance, which includes error handling and recoverability |
particular/servicecontrol-audit | Instance Documentation Container Documentation | The audit instance, which stores audit data, and can be scaled out to multiple audit instances |
particular/servicecontrol-monitoring | Instance Documentation Container Documentation | The monitoring instance, which tracks runtime information like throughput, queue length, and other metrics |
particular/servicecontrol-ravendb | Container Documentation | The database used by the error/audit instances |
particular/servicepulse | App Documentation Container Documentation | The web application that provides a front end for recoverability and monitoring features |
This image is the database used by the particular/servicecontrol and particular/servicecontrol-audit images, based on the official RavenDB image.
The purpose of this image is to provide version parity between ServiceControl and database containers. Users can be sure that a given version of the servicecontrol and servicecontrol-audit container images have been tested with and are known to work with the matching version of servicecontrol-ravendb.
This is the most basic way to start the container using docker run:
docker run -d --name servicecontrol-db \
-v db-config:/etc/ravendb \
-v db-data:/var/lib/ravendb/data \
particular/servicecontrol-ravendb:latest
For all other usage information see the official container documentation.
IMPORTANT: A single database container should not be shared between multiple ServiceControl instances in production scenarios.
latest tagThis tag is primarily for developers wanting to use the latest version. If a release targets the current latest major or is a new major after the previous latest, then the :latest tag is applied to the image pushed to Docker Hub.
If the release is a patch release to a previous major, then the :latest tag will not be added.
We use SemVer for versioning. Release images pushed to Docker Hub will be tagged with the release version.
The latest release within a major version will be tagged with the major version number only on images pushed to Docker Hub. This allows users to target a specific major version to help avoid the risk of incurring breaking changes between major versions.
The latest release within a minor version will be tagged with {major}.{minor} on images pushed to Docker Hub. This allows users to target the latest patch within a specific minor version.
This image is a multi-arch image based on the ravendb/ravendb base image supporting linux/arm64 and linux/amd64.
Content type
Image
Digest
sha256:001e092a7…
Size
296.6 MB
Last updated
8 days ago
docker pull particular/servicecontrol-ravendb