Skip to content

Fix Podman Local VM image resolution - #238

Merged
milind-soni merged 1 commit into
mainfrom
codex/fix-local-vm-image-231
Aug 18, 2026
Merged

Fix Podman Local VM image resolution#238
milind-soni merged 1 commit into
mainfrom
codex/fix-local-vm-image-231

Conversation

@milind-soni

Copy link
Copy Markdown
Owner

What changed

  • Tag the locally built Cua VM image under the explicit localhost/ registry.
  • Add a regression test ensuring Podman commands keep the image local and never resolve it through Docker Hub.

Why

Podman prepends localhost/ to unqualified image names produced by podman build. OpenMausBot later referred to the same image without that prefix, so Podman could miss the local build and try to pull docker.io/openmausbot/cua-local-vm, which does not exist publicly.

This fixes #231.

Validation

  • pnpm vitest run server/container-computer.test.ts — 26 passed
  • pnpm typecheck — passed
  • pnpm test — 103 Vitest files / 1,013 tests passed, broker tests passed, updater tests passed, packaged-server smoke passed

The focused anti-slop lint command continues to report existing findings elsewhere in the two files; the changed lines introduce no new lint findings.

@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@milind-soni, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b4886441-8974-4da3-b3c3-2f9ab5b0f3e0

📥 Commits

Reviewing files that changed from the base of the PR and between 9cee900 and cd38ed0.

📒 Files selected for processing (2)
  • server/container-computer.test.ts
  • server/container-computer.ts

Comment @coderabbitai help to get the list of available commands.

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.

Local VM setup fails: docker://openmausbot/cua-local-vm:driver-0.20.0-v3 pull denied (repo not found on Docker Hub)

1 participant