timescale/timescaledb
timescale
这是一款专为高性能实时分析场景设计的时序数据库，以PostgreSQL扩展的形式提供，能够无缝集成至PostgreSQL生态系统，高效支持时序数据的实时采集、存储与快速分析，为工业监控、物联网数据追踪、***市场实时指标等场景提供便捷且高性能的数据管理解决方案，满足用户对大规模时序数据实时处理与深度分析的核心需求。
257 次收藏下载次数: 0状态：社区镜像维护者：timescale仓库类型：镜像最近更新：9 天前
An open-source time-series database optimized for fast ingest and complex queries. Engineered up from PostgreSQL, packaged as an extension.
Please note: there is no latest tag for this image. See below for further explanation.
Notable tags
latest-pg17- The latest release based on PostgreSQL 17latest-pg16- The latest release based on PostgreSQL 16latest-pg15- The latest release based on PostgreSQL 15latest-pg14- The latest release based on PostgreSQL 14- Each release will also have those corresponding tags, e.g.,
2.18.0-pg17,2.18.0-pg16,2.18.0-pg15, and2.18.0-pg14
Notable links
- Detailed instructions on how to use this Image - [***]
- TimescaleDB itself - https://github.com/timescale/timescaledb
- This docker image's repo - https://github.com/timescale/timescaledb-docker
- Our homepage - [***]
Why is there no latest tag?
In general, it is usually a bad idea to track the latest tag for any Docker image, since you may get unexpectedly upgraded. For TimescaleDB, this is particularly problematic because not only can the version of TimescaleDB change, but also the version of PostgreSQL. If we wanted our latest tag to always be the latest of all dependencies, users could be updated between major versions of PostgreSQL, which requires a pg_upgrade step. That may cause more hassles for the operator than expected.
For these reasons, we do not offer a latest tag, but we do offer a 'latest' equivalent by publishing a latest tag for each PostgreSQL platform we support. For production systems, you should still be explicit about the version you want to use and not these latest tags, but at least you won't have to run a pg_upgrade step unexpectedly.
轩辕镜像配置手册
探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式
Docker 配置
登录仓库拉取
通过 Docker 登录认证访问私有仓库
专属域名拉取
无需登录使用专属域名
K8s Containerd
Kubernetes 集群配置 Containerd
K3s
K3s 轻量级 Kubernetes 镜像加速
Dev Containers
VS Code Dev Containers 配置
Podman
Podman 容器引擎配置
Singularity/Apptainer
HPC 科学计算容器配置
其他仓库配置
ghcr、Quay、nvcr 等镜像仓库
Harbor 镜像源配置
Harbor Proxy Repository 对接专属域名
Portainer 镜像源配置
Portainer Registries 加速拉取
Nexus 镜像源配置
Nexus3 Docker Proxy 内网缓存
系统配置
需要其他帮助？请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
镜像拉取常见问题
使用与功能问题
错误码与失败问题
docker pull 提示 manifest unknown 怎么办？
manifest unknown
docker pull 提示 no matching manifest 怎么办？
no matching manifest（架构）
镜像已拉取完成，却提示 invalid tar header 或 failed to register layer 怎么办？
invalid tar header（解压）
Docker pull 时 HTTPS / TLS 证书验证失败怎么办？
TLS 证书失败
Docker pull 时 DNS 解析超时或连不上仓库怎么办？
DNS 超时
Docker 拉取出现 410 Gone 怎么办？
410 Gone 排查
出现 402 或「流量用尽」提示怎么办？
402 与流量用尽
Docker 拉取提示 UNAUTHORIZED（401）怎么办？
401 认证失败
遇到 429 Too Many Requests（请求太频繁）怎么办？
429 限流
docker login 提示 Cannot autolaunch D-Bus，还算登录成功吗？
D-Bus 凭证提示
为什么会出现「单层超过 20GB」或 413，无法加速拉取？
413 与超大单层
账号 / 计费 / 权限
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"