Supported tags and respective
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What Is CrateDB?
CrateDB is a distributed SQL database that makes it simple to store and analyze massive amounts of machine data in real-time.
Features of CrateDB:
- Standard SQL plus dynamic schemas, queryable objects, geospatial features, time series data, first-class BLOB support, and realtime full-text search.
- Horizontally scalable, highly available, and fault tolerant clusters that run very well in virtualized and containerised environments.
- Extremely fast distributed query execution.
- Auto-partitioning, auto-sharding, and auto-replication.
- Self-healing and auto-rebalancing.
- CrateDB offers the scalability and flexibility typically associated with a NoSQL database and is designed to run on inexpensive commodity servers and can be deployed and run across any sort of network. From personal computers to multi-region hybrid clouds.
The smallest CrateDB clusters can easily ingest tens of thousands of records per second. And this data can be queried, ad-hoc, in parallel across the whole cluster in real time.
How to Use This Image
Spin up this Docker image like so:
$ docker run -p 4200:4200 crate
Once you're up and running, head on over to the introductory docs.
The combinations of Linux kernel version 3.x and Docker >= 1.12 could lead to a major problem with memory accounting causing the kernel to kill the CrateDB process in the container. This problems occurs because of a slab shrinker issue that is fixed in kernel versions >= 4.0.
For issue specific to the CrateDB Docker image, report issues via the
docker-crate GitHub issue tracker
For issues with CrateDB itself, report issues via the
crate GitHub issue tracker
This image is primarily maintained by Crate.io, but we welcome community contributions!
CrateDB is an open core project.
See the CrateDB licensing docs for more information.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.