jason cd977be93d 🐛 Re-apply resolv.conf in init.d phase to beat Docker's async rewrite 🐛 ...

Docker writes /etc/resolv.conf at container start before PID1 launches,
and again asynchronously when the network finishes initializing. The
entrypoint's early copy gets overwritten by Docker's second write.
Re-applying the custom resolv.conf in __run_precopy (init.d phase)
happens after Docker's network setup is complete, so the search . and
options ndots:0 settings stick for the full container lifetime.
- rootfs/usr/local/etc/docker/init.d/08-gitea.sh: copy custom resolv.conf in __run_precopy

rootfs/usr/local/etc/docker/init.d/08-gitea.sh

2026-06-05 15:44:44 -04:00

..

local

🐛 Re-apply resolv.conf in init.d phase to beat Docker's async rewrite 🐛

2026-06-05 15:44:44 -04:00