In past few days, some update has caused docker daemon from starting:
Looks like problem is with configuring the network:
Relevant full excerpt from syslog: gist
Tried docker both from upstream, and debain's own docker.io package.
Running debian testing.
Posted also on docker forum: https://forums.docker.com/t/debian-daem ... ing/142623
Looks like problem is with configuring the network:
Code:
2024-07-22T13:52:48.311618+02:00 host firewalld[1364]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'2024-07-22T13:52:48.434089+02:00 host firewalld[1364]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables: Bad rule (does a matching rule exist in that chain?).2024-07-22T13:52:48.441243+02:00 host firewalld[1364]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).2024-07-22T13:52:48.448046+02:00 host firewalld[1364]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).Tried docker both from upstream, and debain's own docker.io package.
Running debian testing.
Code:
$ uname -aLinux p14s 6.9.9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.9-1 (2024-07-13) x86_64 GNU/Linux\docker-ce & docker-ce-cli 5:27.1.0-1containerd.io 1.7.19-1Statistics: Posted by layr — 2024-07-22 13:44 — Replies 0 — Views 1