Expose resolved Docker endpoint and failure reason in diagnostics#2
Closed
agustif wants to merge 1 commit intoaf/docker-context-resolutionfrom
Closed
Expose resolved Docker endpoint and failure reason in diagnostics#2agustif wants to merge 1 commit intoaf/docker-context-resolutionfrom
agustif wants to merge 1 commit intoaf/docker-context-resolutionfrom
Conversation
Record the resolved Docker endpoint summary and last connection error in daemon startup state, surface them through the docker info API, and include the resolved endpoint details in coast doctor failures. Keep transport behavior unchanged. Refs: coast-guard#65 Co-authored-by: Codex <noreply@openai.com>
Owner
Author
|
Closing in favor of upstream draft PR coast-guard#68. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Draft follow-up for coast-guard#65, stacked on top of coast-guard#61.
This PR improves diagnostics only:
/api/v1/docker/infocoast doctorconnection failuresWhy this is stacked
This depends on the resolver introduced in coast-guard#61. Keeping it stacked makes the diff much smaller than opening a combined branch against upstream
main.Scope
Validation
cargo test -p coast-core test_docker_info_response_serializationCOAST_SKIP_UI_BUILD=1 cargo test -p coast-daemon test_docker_info_disconnected_without_dockercargo test -p coast-cli doctor:: -- --nocaptureRefs: coast-guard#65