Container caddy unhealty - missing /bin/sh?

In my docker installation ( Ubuntu 24.04.1 LTS ) the caddy works but is in state unhealthy. Seems that there is no shell to be used by the health check.
Does anyone see the same or is that related to my installation.

286b39a150d1 lucaslorentz/caddy-docker-proxy:2.9 “/bin/caddy docker-p…” 7 minutes ago Up 7 minutes (unhealthy) 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 2019/tcp seafile-caddy

docker inspect --format “{{json .State.Health }}” 286b39a150d1 | jq
{
“Status”: “unhealthy”,
“FailingStreak”: 18,
“Log”: [
{
“Start”: “2025-01-23T17:17:43.663745054+01:00”,
“End”: “2025-01-23T17:17:43.717843955+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”

Same here:
docker inspect b9c797c7ff53 | jq ‘.[0].State.Health’
{
“Status”: “unhealthy”,
“FailingStreak”: 2852,
“Log”: [
{
“Start”: “2025-01-23T20:00:54.763993455+01:00”,
“End”: “2025-01-23T20:00:54.80283118+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
},
{
“Start”: “2025-01-23T20:01:14.803048312+01:00”,
“End”: “2025-01-23T20:01:14.845252021+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
},
{
“Start”: “2025-01-23T20:01:34.845519298+01:00”,
“End”: “2025-01-23T20:01:34.896643824+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
},
{
“Start”: “2025-01-23T20:01:54.896889908+01:00”,
“End”: “2025-01-23T20:01:54.927705306+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
},
{
“Start”: “2025-01-23T20:02:14.928933176+01:00”,
“End”: “2025-01-23T20:02:14.9791001+01:00”,
“ExitCode”: -1,
“Output”: “OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown”
}
]
}

Hello Inxgeek,

Thanks for reporting. The current image lucaslorentz/caddy-docker-proxy:2.9 dose not have any basic commands like sh, because it use Scratch as the basic image.

You can fix this problem by one of two operations:

Set SEAFILE_CADDY_IMAGE=lucaslorentz/caddy-docker-proxy:2.9-alpine in your .env file.

Good luck,

Yes - that does it.
Thanks.