fix: add --load to buildx to ensure images are available locally

[AaronFeledy]

Summary

• Adds --load flag to buildx command to load built images into the local Docker daemon

Problem

When building v4 services with buildx, the resulting image was sometimes not found:

(HTTP code 404) no such image - No such image: lando/<image>:latest

By default, docker buildx build only stores images in the buildx cache, not the local Docker daemon's image store. When Docker Compose later tries to start containers, it can't find the image. I could only replicate this in WSL using Docker Desktop on Windows.

Solution

Add --load (--output=type=docker) to export the build result into the local Docker daemon, making images immediately available for use. I can't identify any tradeoff from adding this. It just guarantees that the loading that we want to happen actually happens.

---

Note

Ensures images built with Buildx are available to the local Docker daemon.

• Adds --load to buildx build in components/docker-engine.js so --tagged images are loaded locally
• Updates CHANGELOG.md under UNRELEASED to document the fix

^{Written by Cursor Bugbot for commit 6ac2ad9. This will update automatically on new commits. Configure here.}

[netlify]

❌ Deploy Preview for lando-core failed. Why did it fail? →

Name	Link
🔨 Latest commit	6ac2ad9
🔍 Latest deploy log	https://app.netlify.com/projects/lando-core/deploys/697412a1471d0200072bb947