You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some modifications on my codebase, I ran skaffold delete only to receive a simple 'exit status 1' without any informative message.
I escalated the verbosity to INFO and then to DEBUG but found no error message.
INFO[0000] Tags generated in 24.25042ms subtask=-1 task=Build
INFO[0000] Starting render... subtask=-1 task=DevLoop
exit status 1
I noticed that the error occurs after Starting render so I tried skaffold render and it finally displays the full error message (like below)
I think skaffold should give me the full error message.
The same happens when I run skaffold deploy. I get no error message until I try skaffold run, which fails for the same reason but provides the full error message.
According to my memory, the cause of the error was identical. So, maybe, skaffold just fails to deliver the error messages from the render for some commands?
Expected behavior
display full error message like below, which skaffold render provided
running [kubectl --context xxx kustomize overlays/yyy]
- stdout: ""
- stderr: "error: loading KV pairs: env source files: [zzz.env]: evalsymlink failure on 'zzz.env' : lstat zzz.env: no such file or directory\n"
- cause: exit status 1
After some modifications on my codebase, I ran
skaffold delete
only to receive a simple 'exit status 1' without any informative message.I escalated the verbosity to INFO and then to DEBUG but found no error message.
I noticed that the error occurs after
Starting render
so I triedskaffold render
and it finally displays the full error message (like below)I think skaffold should give me the full error message.
The same happens when I run
skaffold deploy
. I get no error message until I tryskaffold run
, which fails for the same reason but provides the full error message.According to my memory, the cause of the error was identical. So, maybe, skaffold just fails to deliver the error messages from the render for some commands?
Expected behavior
display full error message like below, which
skaffold render
providedActual behavior
displays only the status code
Information
I think it's unnecessary
Steps to reproduce the behavior
I think it's unnecessary
The
-vdebug
didn't provide any useful information.The text was updated successfully, but these errors were encountered: