-
Notifications
You must be signed in to change notification settings - Fork 176
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
Improve error message when Zarf can't pull container images when creating a package #25
Comments
#3 is related to user feedback of image actions as well |
Is there a specific reason why being unable to pull the image only a warning? After logging the warning I don't see anything that looks like attempted error recovery. If we do a |
The fatal isn’t the issue here, this is crashing within crane not our code, we need a cleaner way to instrument crane or just replace it. |
I think I must be missing something then. It looks to me like crane is crashing because the If the goal is improving the error message, I think logging a fatal message there would make sense. |
Tbh I haven’t debugged this myself yet, but believe that if either 1. The registry is down or 2. The user doesn’t have creds for that registry. But both of those conditions aren’t directly sent to crane by zarf, crane is reading those states on its own. |
@jeff-mccoy @YrrepNoj do you know what this looks like now in #237? I can go test it myself of course, just wanted to see if you already knew whether this is still an issue or is mostly resolved in #237 |
I actually don't recall sorry |
I think this can be closed. The current design of the CLI gives generic errors across the board for failures that are much cleaner, but to get more details you can run with debug or trace. This was introduced in #237. I think we can discuss changing that broader approach in another issue if it is warranted. |
What I expected:
As a user of Zarf I want it to give me a simple and descriptive error message when it isn't able to pull container images when creating a package, so that I don't have to track down what my issue is.
What I saw:
In this case it was because registry1.dso.mil was down for a few minutes, but I've also seen this error message when I don't have my credentials for the container registry set properly
Migrated from https://repo1.dso.mil/platform-one/big-bang/apps/product-tools/zarf/-/issues/39
The text was updated successfully, but these errors were encountered: