
This folder contains a Dockerfile and other configs required to build the pytest container that runs the CircleCI job for the testing suite.
All of the examples given here assume the current working directory is the root of the https://github.com/databricks/docs repository.
Make sure you reference the correct version of the feature store wheel in the Dockerfile.
Also check the version tag of the pytest executor in the CircleCI config file and increment the version number. At the time of writing that version is v0.1.4.
yamlexecutors: pytest: docker: - image: databricksdocs/pytest:v0.1.4
So for the purposes of this document we'll be building and pushing v0.1.5.
shexport pytest_version=v0.1.5 docker build -t databricksdocs/pytest:${pytest_version} -f shared/docker/pytest/Dockerfile .
You'll want to get some coffee or go to a movie or something while this builds. There are a lot of Python dependencies required to run the feature store code and almost none of them have binary versions available so the build will be doing some compiling. Give it a good 30-40 minutes to be sure.
If you've not died of old age when the build is done, you should check that the built image works. This is simple and fast, all you have to do is run the image against your local copy of the docs repository.
shexport ext_dir=$(cd shared/extensions&&pwd) docker run --rm -v $(pwd)shared/extensions:/extensions --rm databricksdocs/pytest:${pytest_version} pytest -l -s -vv /extensions
If you get valid test results in the output of this run command you know the build worked, you've got a working pytest image.
Now that you know the image works you can push it to the https://hub.docker.com/repository/docker/databricksdocs/pytest Docker repository.
shdocker push databricksdocs/pytest:${pytest_version}
Finally, update the pytest executors in both of the CirleCI config files.
The executors section should be at the top of the file, make sure to replace the version that's there with the one you just built.
yamlexecutors: pytest: docker: - image: databricksdocs/pytest:v0.1.5
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 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 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务