det deploy local cluster-up fails (wrong determinedai/determined-agent image pull)
See original GitHub issueFollowing the official example for a basic workstation I do:
det deploy local cluster-up
The determinedai/determined-agent:0.18.4
gives error at pulling so I manually pulled latest
and repeat det deploy ...
and it is fixed.
The default determined-agent
image reference should be updated as it is now stoping basic installation.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Install Determined Using det deploy
This document shows how to deploy Determined locally or in a production cluster using the det deploy command-line tool, which automates the process...
Read more >Kubernetes ImagePullBackOff: Troubleshooting With Examples
One such error is ImagePullBackOff. It typically shows up when the kubelet agent instructs the container runtime and can't pull the image from...
Read more >docker - kubernetes cannot pull local image - Stack Overflow
So you have the image on your machine aready. It still tries to pull the image from Docker Hub, however, which is likely...
Read more >kubelet fails to pull local image while nodes can docker pull ...
I am using Terraform to deploy the pods, via YAML is the same. It doesn't matter if I can docker pull/push images to...
Read more >[BUG] Cluster creation fails when specifying k3s image v1 ...
k3d cluster create --config k3d/kubeflow-cluster.yaml INFO[0000] Using ... Same error occurs using image: rancher/k3s:v1.19.16-k3s1-amd64 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I bought a Cat 6a ethernet. Docker TLS problem solved. This is crazy.
Thanks for all your support!
This is odd, I’ve never seen anything like it. Can you reproduce it on another machine?
My random guesses would be:
Either way, it doesn’t seem to be a determined issue, but I’d love to know what the root cause was out of general curiousity.