Recommend closing resolved or non-actionable issues

## Summary

I reviewed a batch of open issues in this repo and identified 15 that appear to be resolved, stale, invalid configuration, upstream/environment limitations, or otherwise not actionable as Colima bugs. Below is each issue with a suggested closure reason.

If you agree, the maintainer can bulk-close with:
```sh
gh issue close 1138 1436 1038 1065 777 1222 1480 1533 756 560 847 434 524 1023 1427 --repo abiosoft/colima
```

---

## Issues to close

- [ ] **#1138** — Unable to run SQL Server 2017 container with colima v0.7.5
> Resolved. The original reporter confirmed: “As of colima v0.9.1 the issue no longer persists.” Suggested close reason: `completed`.

- [ ] **#1436** — Colima injects weird HTTP(S)_PROXY environment variable into containers
> Resolved on the development build. Maintainer asked for confirmation on `brew install --head colima`, and a user confirmed the proxy variables seem to be fixed there. Suggested close reason: `completed`.

- [ ] **#1038** — Critical bug affecting v0.6.9 that causes docker, compose and colima itself to stale and crash
> Resolved by later disk-image/startup work. Maintainer said the disk image download/expansion process had been reworked, and users later confirmed the issue was solved or no longer reproducible on newer builds. Suggested close reason: `completed`.

- [ ] **#1065** — k3s airgap image SHA validation failure
> Resolved by using a newer k3s version. The failure was tied to an old/default k3s version that was no longer available/valid; a commenter confirmed specifying a newer version fixed it. Suggested close reason: `completed`.

- [ ] **#777** — colima start fails due to “QEMU has already exited” - QEMU 8.0.4
> Resolved upstream in QEMU packaging. AkihiroSuda noted the issue was fixed in the QEMU `8.1.0-1` bottle. Later comments are mostly state-reset/workaround discussion. Suggested close reason: `completed`.

- [ ] **#1222** — --k3s-arg=--disable=... does nothing but --kubernetes-disable still works
> Not a Colima bug. Maintainer clarified that the argument needs to be quoted, and follow-up help/docs examples were addressed by #1386. Suggested close reason: `completed` or `not planned`.

- [ ] **#1480** — Using dnsHosts:host.docker.internal:host.docker.internal prevents Colima from starting
> Invalid configuration. Maintainer explained this creates an infinite DNS resolution loop, and the reporter replied that the issue can be closed if the config is incorrect. Suggested close reason: `not planned`.

- [ ] **#1533** — Missing `mounts:` no longer defaults to mounting home directory
> Expected behavior since v0.10.0. Maintainer clarified that no `mounts` key is equivalent to `mounts: null` and disables mounts; reporter acknowledged it is not a bug. Any remaining work is documentation wording. Suggested close reason: `not planned`.

- [ ] **#756** — npm install runs into TAR_ENTRY_ERROR EPERM error
> Likely not a Colima issue. The reporter explicitly noted it may have nothing to do with Colima and can be closed if no Colima change is required. Suggested close reason: `not planned`.

- [ ] **#560** — Resolve dns of `host.docker.internal` to vm’s reachable IP
> Not needed for Docker Desktop parity. The reporter retested Docker Desktop, concluded it does not expose `host.docker.internal` on the host either, and said the issue can be closed. Suggested close reason: `not planned`.

- [ ] **#847** — Doesn’t install on Mojave via MacPorts
> Upstream packaging/dependency issue. The failure is upstream of Colima and tracked in MacPorts/SPICE. Suggested close reason: `not planned`.

- [ ] **#434** — Running Without KVM?
> Upstream/platform limitation. Running under WSL2 without KVM is blocked by QEMU/KVM requirements and Lima/Windows support, not Colima itself. The reporter also said it can be closed if desired. Suggested close reason: `not planned`.

- [ ] **#524** — vm driver `vz` needs macOS 13 or later
> Homebrew/Lima setup issue. Later comments indicate reinstalling Lima after OS upgrade fixed it; this does not appear to require a Colima code change. Suggested close reason: `not planned`.

- [ ] **#1023** — Unable to run on macOS GitHub runner with brew installation
> GitHub Actions runner limitation. GitHub-hosted macOS ARM runners do not support the virtualization capability Colima needs. Suggested close reason: `not planned`.

- [ ] **#1427** — Running Colima with GitHub Actions on `macos-latest`
> Apple/GitHub hosted-runner limitation. Maintainer confirmed there are no real alternatives until Apple supports nested virtualization on macOS guests. Suggested close reason: `not planned`.

---

_This triage was done by reviewing each issue's comments and the current project context. Happy to discuss any of these individually._