saltstack/saltSalt Project has archived the
saltdockerrepository, and the containers will no longer be updated. These containers were not officially supported, they were initially created by the community for testing purposes and the core team only facilitated the publishing of the containers. For more information, visit The Salt Project Blog: saltdocker Repository Now Archived
Dockerfile links3006.4, 3006.3, 3006.2, 3006.1, 3006.0, latest3006.0rc3, 3006.0rc2, 3006.0rc1, rc3005.4, 3005.3, 3005.2, 3005.1, 30053004.2, 3004.1, 3004WARNING These containers are not officially supported, they were initially created by the community for testing purposes and the core team only facilitates the publishing of the containers.
Salt is a configuration management tool / orchestration platform.
This image contains a running salt-master and salt-api process, which can be used to control other salt-minions.
!SaltProject
console$ docker run --name salt --hostname salt -p 4505-4506:4505-4506 -p 8000:8000 -e SALT_SHARED_SECRET=mysecretpassword -d saltstack/salt
The default salt user is created but the shared secret is specified in the /etc/salt/master.d/api.conf.
The api listens on port 8000 with ssl enabled.
There are many ways to extend the salt image. Without trying to support every possible use case, here are just a few that we have found useful.
The Salt image uses several environment variables which are easy to miss. While none of the variables are required, they may significantly aid you in using the image.
SALT_MASTER_CONFIGA JSON object. This variable is dumped to /etc/salt/master.d/master.conf and can be used to provide extra config for the salt master.
SALT_API_CONFIGA JSON object. This variable is dumped to /etc/salt/master.d/api.conf, and defaults to the following.
yamlrest_cherrypy: port: 8000, ssl_crt: /etc/pki/tls/certs/localhost.crt ssl_key: /etc/pki/tls/certs/localhost.key external_auth: sharedsecret: salt: ['.*', '@wheel', '@jobs', '@runner'] sharedsecret: $SALT_SHARED_SECRET
SALT_SHARED_SECRETIf this environment variable is set, it will set the sharedsecret variable for using the salt-api with the salt user.
If the salt-master is not configured immediately at the start, the master config can be updated using wheel modules via the salt api using the Salt Config Wheel Module
In order to make volumes available to the salt user in the container, assign the group id 450 to the directory before it mounting it on the container.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务