fix: force client.DefaultDockerHost for supabase start when using colima#5074
Open
hk220 wants to merge 2 commits intosupabase:developfrom
Open
fix: force client.DefaultDockerHost for supabase start when using colima#5074hk220 wants to merge 2 commits intosupabase:developfrom
hk220 wants to merge 2 commits intosupabase:developfrom
Conversation
…sock socket file inside it.
hk220
changed the title
Author
|
Sorry, I fixed the typos in this title and description. |
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
#5073
What is the new behavior?
Force the use of client.DefaultDockerHost when running supabase start with colima