douglascamata / douglascamata/setup-docker-macos-action
No route to host since macos-15-intel with `colima-network-address: true` set
- Dominant language
- Shell
- Stars
- 71
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
A recent change seems to break the `colima-network-address: true` usage.
The VM does start, the `colima list` says the VM have an IP, but we can't reach it from host. Constantly getting "No route to host".
Worked perfectly fine with:
- macos-12 (now deleted)
- macos-13 (pending deletion on December)
- macos-14-large (but costly... can't use it much)
stopped working with `macos-15-intel`.
I am completely clueless on why such silent failure would occurs and I have difficulties on getting my hand on a MacOS instance.
Tried to completely disable the firewall but no luck on that side.
regards,
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the action's handling of the `colima-network-address: true` option and reproduce the workflow on a `macos-15-intel` runner, comparing it with macos-12, macos-13, and macos-14 behavior. Confirm completion when the started VM's advertised IP is reachable from the host without “No route to host”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, macos, shell
- Domain
- ci-cd, devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100