-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Getting started docs - ErrImagePull
on whalesay
#13388
Comments
I found some discussion related to this here: #12767 (comment) What's the resolution? |
Per that discussion, it's an upstream issue unfortunately with the image: docker/whalesay#6. Per the issue, I also tweeted out at Docker to try to get their attention that way, and it got some retweets, but no response unfortunately: https://x.com/agilgur5/status/1790084420642255219 😕
In this case, it would be to use a different image from Same root cause as #11858 as well |
ErrImagePull
on whalesay
Closing as the resolution to this would be the same as that issue |
Ok. I understand the problem and the desire to use whalesay. However as that isn't forthcoming, perhaps the docs and the getting started example could be re-worked, for example to use an alpine image or busybox or any other popular working image that would let you just echo some text or whatever was required. This would mean re-working the getting started example - as things stand it's not a good getting started experience. If the issue you have linked will resolve the getting started experience then I am happy this can be closed. |
Yea I was thinking the exact same to switch to
Unfortunately, it means re-working a lot more than that: quick search says PRs certainly welcome though!
#11858 is regarding Also I did get a response from Docker Support in docker/whalesay#6 (comment) (I emailed them after you raised this, unfortunately it's not quite a sufficient response). |
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
Never used argo before, I attempted to follow the Getting started page. It seems to fail pulling the image. I did not expect this.
After successfully installing argo server / controller in a k8s namespace, and the cli, I submitted the test workflow as instructed here
After some time I see the message transition from
PodInitializing
toErrImagePull
then eventually to
this seems to cycle to
ErrImagePull
again.After 4 mins the workflow still hasn't executed seemingly due to some issue with pulling the image.
Version(s)
v3.5.8
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
As per the docs its this one here:
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: