moby-engine: remove daemon.json with backported fix

[hbeberman]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

When upgrading to moby-engine version 25 we brought in a new daemon.json file to inform the newer moby-engine version of docker-proxy's location. Adding daemon.json to the package regressed several use cases, instead we'll rely on backporting a recent upstream change (moby/moby#47804) that implicitly looks for docker-proxy in libexec so that we can drop daemon.json.

Change Log

• Backport Lookup docker-proxy in libexec paths moby/moby#47804 so moby-engine finds docker-proxy in libexec
• Remove daemon.json from our moby-engine package.

Does this affect the toolchain?

NO

Associated issues

• Issue reported (and fixed) in Azure Linux 2.0 moby-engine package should not include /etc/docker/daemon.json #8961

Test Methodology

• Local package build
• Buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=619256
• Updated the package on a running system and observed that moby-engine is still able to find docker-proxy after the upgrade.