Skip to content

Fix colima docs - #7902

Merged
eddumelendez merged 1 commit into
mainfrom
fix-colima-docs
Dec 2, 2023
Merged

Fix colima docs#7902
eddumelendez merged 1 commit into
mainfrom
fix-colima-docs

Conversation

@eddumelendez

Copy link
Copy Markdown
Member

No description provided.

@eddumelendez
eddumelendez requested a review from a team December 2, 2023 23:08
@eddumelendez eddumelendez added this to the next milestone Dec 2, 2023
@eddumelendez
eddumelendez merged commit f0c5759 into main Dec 2, 2023
@eddumelendez
eddumelendez deleted the fix-colima-docs branch December 2, 2023 23:09
@cuichenli

Copy link
Copy Markdown

Hi @eddumelendez, I apologize for the inconvenience caused. I'm unsure if I've overlooked anything, but based on the new documents, I'm unable to establish a connection to the docker daemon. However, if I refrain from starting colima without the --network-address parameter and avoid specifying the TESTCONTAINERS_HOST_OVERRIDE, the connection seems to work.

By the way, I'm currently accessing this while connected to a VPN, and I've attempted to access the $(colima ls -j | jq -r '.address') from my host, but it appears that I'm unable to establish a connection to it.

Therefore, I'm curious to know if these two additional steps are actually necessary.

@bcoughlan

Copy link
Copy Markdown

Same result as @cuichenli, on Mac M1. The working setup for me is:

export DOCKER_HOST=unix:///Users/myuser/.colima/docker.sock
export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/Users/myuser/.colima/docker.sock
export TESTCONTAINERS_RYUK_DISABLED=true

fokion pushed a commit to fokion/testcontainers-java that referenced this pull request Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants