-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8S点对点Runp模式运行测试作业时,任务一直pending #371
Comments
用新版本再重试下看看呢 |
我是用的就是latest版本呀,不知道您说的新版本什么意思呢 |
好的,看上去是kuscia里去拉secretflow镜像出现的问题,我们这边确认一下 |
刚才阿里云镜像仓库有抖动。这个错误是因为没有从远程仓库(secretflow-registry.cn-hangzhou.cr.aliyuncs.com/secretflow)拉取到本地导致。现在应该是恢复了。现在应该可以了 |
您部署完以后手动到pod 执行下k8s apply试下呢 |
kubectl apply -f AppImage.yaml 么?执行了这个的 |
我也遇到这个问题,我设置的私有仓库,仍然是从本地拉取镜像,同样的错误,怎么解决的 |
1.私有仓库,这个配置暂不可用 |
是runp,如果不能拉远端的镜像,如何能够引入appimage的镜像 |
kuscia-secretflow这个镜像在构建的时候,已经将sf镜像打进去了。所以确认下depolyment里用的是kuscia-secretflow镜像 |
Stale issue message. Please comment to remove stale tag. Otherwise this issue will be closed soon. |
Issue Type
Others
Search for existing issues similar to yours
No
Kuscia Version
latest
Link to Relevant Documentation
No response
Question Details
通过下面deployment.yaml拉起pod,使用的镜像是latest
进入Pod后通过下面AppImage.yaml,创建appimage,使用的镜像是1.7.0b0:
执行脚本
scripts/user/create_example_job.sh
运行测试任务,任务一直pending
查询任务详情:
报错为镜像找不到,将镜像换成 1.6.0b0也是同样的报错。
但是在宿主机上1.7.0b0镜像存在。
求解答。
The text was updated successfully, but these errors were encountered: