crate docker image 镜像
source link: https://hub.docker.com/_/crate
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
docker pull crate
# Quick reference
-
Maintained by:
Crate.io -
Where to get help:
project documentation, StackOverflow, Slack, or paid support
Supported tags and respective Dockerfile links
Quick reference (cont.)
-
Where to file issues:
https://github.com/crate/docker-crate/issues -
Published image artifact details:
repo-info repo'srepos/crate/directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images PRs with labellibrary/crate
official-images repo'slibrary/cratefile (history) -
Source of this description:
docs repo'scrate/directory (history)
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 crateOnce you're up and running, head on over to the introductory docs.
See also:
Issues
Memory Accounting
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.
Others
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
Contributing
This image is primarily maintained by Crate.io, but we welcome community contributions!
See the developer docs and the contribution docs for more information.
License
CrateDB is licensed under the Apache License 2.0.
See LICENSE 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 repo-info repository's crate/ directory.
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.
Recommend
-
25
How I’ve found vulnerability in a popular Rust crate (and you can too) I have recently discovered a zero-day vulnerability
-
26
The Rust ecosystem has lot of excellent crates, and many more new ones being published. I believe one is missing, though, and I’d really like to see it happen: a cross-platform abstraction for 2D graphics. In this post I...
-
22
Today we released a tool, siderophile , that helps Rust developers find fuzzing targets in their codebases. Siderophile trawls your crate’s dependencies a...
-
10
What Are Bitfields? The C programming language is a product of a time where it was important to use as few resoures as possible. Memory was measured in kilobytes rather than gigabytes as we do today. Bitfields of...
-
30
A Rust driver crate for the ADXL355 digital accelerometer. This driver accepts an
-
7
Introducing Glommio - a Thread-per-Core Crate for Rust & LinuxGlauber CostaPublished: November 2, 2020
-
5
Cross-crate inlining Feb 2, 2012 Cross-crate inlining (CCI) refers to the ability to inline a function across crate boundaries. In Rust, a “crate” is the unit of compilation, rather than an individual file as in C or C+...
-
4
The First Crate Polishing Workshop 27 February 2017 On Friday, the 24th of February, we held the first Crate Polishing Workshop in Darmstadt, Germany at Cowo21 (German site...
-
14
Lints That Collect Data Per Crate 09 October 2015 (works with Rust 1.5.0-nightly-20151009) Update (See below) Here’s a short description of a technique I encounte...
-
10
9 July 2019Migrating a crate from futures 0.1 to 0.3 I recently migrated a small/medium-sized crate from Futures 0.1 to 0.3. It was fairly easy, but there were some tricky bits and some things that were not well documente...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK