Skip to content
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

Print firewall notice if colima network cannot be detected #68

Merged
merged 1 commit into from
Sep 20, 2024

Conversation

avsej
Copy link
Member

@avsej avsej commented Sep 20, 2024

This is how it would look like on recent OSx with enabled firewall:

-- Docker Configuration
Would you like to configure Docker Deployments? [Y/n]:
Checking for Colima installation at `/Users/user/.colima/default/docker.sock`... found.
Checking for Docker installation at `/var/run/docker.sock`... not found.
What docker host should we use? [unix:///Users/user/.colima/default/docker.sock]:
Pinging the docker host to confirm it works...
Success!
Listing docker networks:
  none
  bridge
  host
This appears to be colima, attempting to identify network information.
Attempting to fetch colima instance data.
Failed to detect colima address with 'colima ls'.
* make sure colima started with '--network-address'
* try to disable firewall at 'System Settings' -> Network -> Firewall.
Identified colima address of ``
Network identification failed, cannot auto-create dinonet network...What docker network should we use? [dinonet]:

@avsej avsej requested a review from brett19 September 20, 2024 17:56
@brett19 brett19 merged commit 1484827 into couchbaselabs:master Sep 20, 2024
4 checks passed
@avsej avsej deleted the firewall-notice branch September 20, 2024 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants