puppet/pdkThis repository provides official docker images for the Puppet Development Kit (PDK).
Images are published to Docker Hub at [***]
The following image tags are available from Docker Hub:
latest: Meta-tag which will always point to the latest stable PDK releasenightly: Meta-tag which will always point to the latest PDK release which may
be a pre-release buildAdditionally there are version-specific tags for every PDK release that makes it on
to [***] for example 1.12.0.0 (stable release),
1.13.0.0.pre.2.g9c61983 (nightly pre-release).
To learn more about the PDK, visit [] and []
The PDK docker images are currently based on a fairly minimal Ubuntu 18.04 image.
From there, a PDK .deb package is installed. Since there is a lag time between
when changes are merged to the puppetlabs/pdk or puppetlabs/pdk-vanagon
Github repositories and when a .deb package with the changes is actually available,
we can't trigger Docker Hub builds immediately on commit/tag to either of those
repositories.
Instead, we have configured a periodic Jenkins job (internal only right now, sorry)
which runs the update-pdk-release-file.rb script in this repo and then checks to see
if that resulted in any changes to the pdk-release.env file. This file contains
environment variables which indicate what the most recent PDK release package available
on the Puppet nightlies
server is. pdk-release.env is then used by the Dockerfile (via install-pdk-release.sh)
to build an image containing the specified release package.
If changes to pdk-release.env are detected by the Jenkins job, a new commit is
made to the master branch of this repo. (If the release is identified as a final
release, the stable branch is rebased on master to pick up this change as well.)
Lastly a new tag is made with the version number of the new release and then Jenkins
pushes all commits and tags back to this repo.
Finally, Docker Hub is configured to watch the this repo and build/tag new images automatically based on the branch or tag that received new commits.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务