
Dockerfile and any other required configuration required to build the Databricks docs Sphinx build image.
The build process is simple. You start from the root of the https://github.com/databricks/docs repository, declare the version of the container you intend to build, then build the image.
Image versions follow (very roughly) semantic versioning. To find the next image version number you can simply check the current image version and increment the appropriate part of the version number based on the number and depth of the changes you're making.
bashexport IMAGE_VERSION=v0.0.4 docker build -t databricksdocs/sphinx:${IMAGE_VERSION} -f shared/docker/sphinx/Dockerfile .
If you need to make changes to the image and don't necessarily care to wait for the whole image build process to complete you can run the current version of the image, make the changes you need to make, then commit that container as a new version of the image with a lowercase letter appended to the end of the existing version.
bashdocker run --rm --name sphinx -it databricksdocs/sphinx:${IMAGE_VERSION} bash
Update the container with your changes from the provided prompt, then commit and push the updated version.
bashdocker commit -m "Updated sphinx image" sphinx databricksdocs/sphinx:${IMAGE_VERSION}a docker push databricksdocs/sphinx:${IMAGE_VERSION}a




探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务