GoogleContainerTools/skaffold

Confusion between Jib and Skaffold output

Open

#3,978 建立於 2020年4月18日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Go (12,822 star) (1,416 fork)batch import
area/loggingbugbash/q4-2022help wantedkind/design discussion

描述

We've had a number of situations now where users have encountered hard-to-diagnose authentication errors when using Jib with Skaffold. Often the image build succeeds with Jib but then Skaffold exits with a failure. For example, this StackOverflow question has in the logs:

[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  20.058 s
[INFO] Finished at: 2020-04-15T08:45:57+03:00
[INFO] ------------------------------------------------------------------------
Pruning images...
FATA[0024] exiting dev mode because first build failed: build failed: building [registry.demo/springtokube]: build artifact: getting image: GET http://registry.demo/v2/: : Not Found

We should make a clearer difference between builder output and Skaffold's output. Perhaps prefixing builder output with > or | ? Or clear begin and end markers.

And this error message doesn't indicate why it's trying to get the image.

貢獻者指南

技術棧
go
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GoSkaffold CLIterminal output formatting
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the Skaffold source code to identify where builder output (like Jib) is printed. Look at how Skaffold formats its own output and where the error message 'getting image: GET http...' originates. Consider adding prefix like '> ' or markers to distinguish builder logs from Skaffold logs. See linked StackOverflow for context.