Docker compose "init: true" causes container start failure

[ihatemyisp]

Describe the bug

After installing updates today, I am unable to get any Compose stack that uses "init: true" to launch properly. They start but fail with "exec /sbin/docker-init: no such file or directory".

Reproduction steps

1. "docker compose up" on any stack with "init: true"

Expected behavior

The stack comes up and functions properly.

Additional context

I have also tested using just a standard "docker run --init" and it fails as well. i.e., "docker run --init nginx:1-alpine"

I have tested manually setting the init-path and forcing "init: true"

[ihatemyisp]

Rolling back with tdnf failed...

Disabled photon-updates, enabled photon-release, ran a distro-sync and I'm back in business.

Would still like to move back to updates but I need this stack up and running.

[dcasota]

Adding -v to the Docker command (docker run -v --init nginx:1-alpine) resolves the issue. The most recent PR related to "--init" is Lookup docker-proxy in libexec paths.

The issue is reproducible when starting from a Ph5 image. After updating docker to 27.3.1-6.ph5 , the issue appears.

VM installed from e.g. photon-5.0-2abb50975.x86_64.iso, fresh compiled on April 24th 2025 with original Ph sources, 2gb ram + 8gb hd, mbr boot, minimal, hypervisor-optimized, no stig hardening.
# (logged-in as root)
systemctl enable docker
systemctl start docker
tdnf install docker-compose -y  

docker run --init nginx:1-alpine # starts successfully
# (ctrl-c to terminate)  

reboot
# (logged-in as root)
docker run --init nginx:1-alpine # starts successfully  

reboot
# (logged-in as root)
tdnf install -y tini
docker run --init nginx:1-alpine # starts successfully  

# (ctrl-c to terminate)
tdnf update docker -y
docker run --init nginx:1-alpine # fails

[ihatemyisp]

Broken in docker 27.3.1-7.ph5 as well.