Octol1ttle 330e717403 fix(systemd): start Docker engine *after* DNS resolution is ready ...

On systems using systemd to autostart Docker on boot, containers might encounter a problem where they will not have any DNS access until the container is restarted manually. This PR fixes this issue by requiring that the Docker engine service starts after nss-lookup.target. This target is reached when DNS resolution is available. See https://wiki.archlinux.org/title/Systemd#Running_services_after_the_network_is_up (paragraph "If a service needs to perform DNS queries...")

Signed-off-by: Octol1ttle <l1ttleofficial@outlook.com>

2024-11-04 15:57:24 +05:00

..

openrc

fix: Normalize RLIMIT_NOFILE to sensible defaults

2023-08-07 12:37:14 +12:00

systemd

fix(systemd): start Docker engine *after* DNS resolution is ready

2024-11-04 15:57:24 +05:00

sysvinit-debian

fix: Normalize RLIMIT_NOFILE to sensible defaults

2023-08-07 12:37:14 +12:00

sysvinit-redhat

run shfmt

2020-03-03 12:27:49 +09:00