NetworkCatsandClaude Opus 5.5 712a82698e Fix Docker failing to start on first deploy ...

The firewall role's "Reload systemd" handler shadowed the docker role's
handler of the same name, and its flush_handlers ran the pending Docker
restart right after base lowered fs.nr_open, without a daemon-reload.
Docker then started without its LimitNOFILE override and systemd could
not apply the default limit (status=205/LIMITS).

Reload systemd inline in the firewall role instead of through a
handler, so other roles' handlers keep running at the end of the play,
and reload before ensuring Docker is running so a host left in this
state recovers on the next deploy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-22 21:41:25 +08:00

..

roles

Fix Docker failing to start on first deploy

2026-10-22 21:41:25 +08:00

playbook.yml

Restrict HTTPS to Cloudflare with UFW on the host

2026-10-22 21:13:48 +08:00