[central] intermittent test failure: check-docker-context.sh: No such image

[alxndrsn]

https://github.com/getodk/central/actions/runs/21956300509/job/63421313692?pr=738

[check-docker-context.sh] Removing docker image...
Error response from daemon: No such image: sha256:5a39bb8d1f878790b0c024f71a2af7de001c172c57db8d08ae9ba3eeeeb8c7d1
Error: Process completed with exit code 1.

[alxndrsn]

This with --iidfile is the documented expected behavior that scripts can rely on that we shouldn't break, as opposed to pattern matching from the output.

• [RFC] Add some output to logs for backward compat moby/buildkit#1155 (comment)

So probably the fix would be to use --iidfile (https://docs.docker.com/reference/cli/docker/buildx/build/).

[alxndrsn]

https://github.com/getodk/central/actions/runs/22072565354/job/63780555930?pr=1648

[8](https://github.com/getodk/central/actions/runs/22072565354/job/63780555930?pr=1648#step:3:1659)

#13 importing to docker
#13 DONE 0.0s
[check-docker-context.sh] File count:  1595
[check-docker-context.sh] Total size: 55.692 MB
[check-docker-context.sh] Removing docker image...
Error response from daemon: No such image: sha256:1e35526cd17f5c709168ef6563d525e1f919dcac5da273677f13ebfc69da88d2
Error: Process completed with exit code 1.

[alxndrsn]

Happening repeatedly on #1648

[matthew-white]

Closed by #1649.

[lognaturel]

@matthew-white do you know why you still had to close this one by hand? I thought we expected all "Closes" patterns to work now!

[matthew-white]

I think it's because the new auto-close commits are still just on next, not master. You can see them in #1636. Maybe we could pull them into the patch release somehow. Or just cherry-pick them right away. I feel like CI-related commits can often go straight onto master.