supabase / cli / 30362784918

65%

develop: 65%

push

github

fix(cli): diagnose unrunnable images (#5966)

## TL;DR

`supabase start` reported health-check failures by raw Docker id with no
way forward — it
now names the container, its image, and the command to fix it.

## Prob

When a container's cached image can't be executed:

```
<a class=hub.com/supabase/cli/commit/99a635a072a8e0b2d7e56f9a619a5b4027bdeef7">99a635a0702102508383900b78b8cc18b container logs:
exec /mailpit: exec format error
99a635a072a8e0b2d7e56f9a619a5b4027bdeef702102508383900b78b8cc18b: container is not ready: unhealthy
Try rerunning the command with --debug to troubleshoot the error.
```

You can't tell which service died, and `--debug` only logs HTTP
requests.

## Sol

```
supabase_inbucket_bredbox container logs:
exec /mailpit: exec format error
supabase_inbucket_bredbox: container is not ready: unhealthy
supabase_inbucket_bredbox's image public.ecr.aws/supabase/mailpit:v1.30.2 could not be executed ("exec format error").
Either the cached copy is corrupt, or it was built for a different architecture.
Remove the cached copy with docker (or podman), then run supabase start again:

  docker image rm -f public.ecr.aws/supabase/mailpit:v1.30.2
```

Containers are watched by name, and `exec format error` attaches the
affected
image and the command to remove it.

## Ref

- closes #5952

11288 of 17283 relevant lines covered (65.31%)

10.53 hits per line