pulumi/pulumi-dotnet-8.0This image is an alternative to the Pulumi docker image. The pulumi/pulumi image is quite large because it has to bundle all the SDKs that Pulumi supports:
This container is a slimmer container for the specific SDK. It contains the pulumi binary, the pulumi language runtime for that SDK and any additional necessary language components..
We build a matrix of images for differing Pulumi language SDKs and operating systems. The OS base images we use are:
The base and debian images are available for ARM64 and AMD64 architectures, while the UBI images are only available for AMD64.
The base image just contains the pulumi binaries and language runtimes, but not the SDK runtimes. If you use the base image, you'll have to install Go/Python/Dotnet/NodeJS yourself. The image format is:
pulumi/pulumi-base:<PULUMI_VERSION>-<OS>-<ARCH>
The default image without the OS is based on Debian AMD64, and can be used like so:
pulumi/pulumi-base:<PULUMI_VERSION>
Images with the SDK runtimes are generated in the following format:
pulumi/pulumi-<PULUMI_SDK>:<PULUMI_VERSION>-<OS>-<ARCH>
The default image without the OS suffix is based on Debian AMD64, and can be used like so:
pulumi/pulumi-<PULUMI_SDK>:<PULUMI_VERSION> pulumi/pulumi-<PULUMI_SDK>:latest
Each of the images are much smaller than the combined Pulumi container. They are in the region of approx 150-400MB (compressed size) depending on the operating system it has been built on and the dep
We currently build images based on both Debian Bookworn and with the RedHat Universal Base Image/
The UBI images use microdnf as a package manager, not yum. See this page for more information.
To run a Pulumi command in a container, pass a bash command to the container:
docker run --rm -e "PULUMI_ACCESS_TOKEN=$PULUMI_ACCESS_TOKEN" -v $(pwd):/pulumi/projects $IMAGE bash -c "pulumi install && pulumi preview -s $STACK"
These images do not include additional tools you might want to use when running a pulumi provider. For example, if you're using the pulumi-kubernetes with Helm, you'll need to use these images as a base image, or install the helm command as part of your CI setup.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务