"Image is in use by a container" error during vagrant destroy when docker provider cannot remove in-use image

[eszense]

Context

Unexpected error during vagrant destroy regarding failure to remove in-use docker image has previously been fixed in #7245

Current Bug

The problem recur when Docker is connected to a podman backend.
This is because the slight difference in error text is not recognised.

Reproduction

1. Create two identical project

projectA/
  Dockerfile
  Vagrantfile
projectB/
  Dockerfile
  Vagrantfile

Dockerfile:

FROM alpine
RUN touch /test

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.provider "docker" do |d|
    d.build_dir = "."
    d.remains_running = false
  end
end

2. Run

cd projectA; vagrant up
cd ../projectB; vagrant up && vagrant destroy -f

3. Current behavior: throws Error

A Docker command executed by Vagrant didn't complete successfully!
The command run along with the output from the command is shown
below.

Command: ["docker", "rmi", "52a6cd7780a1", {:notify=>[:stdout, :stderr]}]

Stderr: Error response from daemon: image 52a6cd7780a1 is in use: image used by 661ef8666be33d1b951cb1526d8b81636b1a807d707c77d00fb44ad2f6a7313e: image is in use by a container: consider listing external containers and force-removing image


Stdout: 

Environment

% vagrant -v
Vagrant 2.4.1

% docker version
Client:
 Version:           27.4.1
 API version:       1.41 (downgraded from 1.47)
 Go version:        go1.22.10
 Git commit:        b9d17ea
 Built:             Tue Dec 17 15:42:24 2024
 OS/Arch:           darwin/arm64
 Context:           default

Server: linux/arm64/fedora-40
 Podman Engine:
  Version:          5.0.3