Docker not working on reboot with Fpbx 17 beta

Beta Program Issues
1

I’m noticing that, on reboot, I get a weird message from Docker:

docker run --name=QM --volume=/opt/queuemetrics_data:/data -p 8080:8080 --restart unless-stopped -d loway/queuemetrics

595d3bad743d47f75546016dc506544e7836011b2f21d100e5fb43c23fc9b333
docker: Error response from daemon: driver failed programming external connectivity on endpoint QM (2775f2460131d4e3bdea725f63b4edc79633833cb751417d07fa9874489555e7): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 8080 -j DNAT --to-destination 172.17.0.2:8080 ! -i docker0: iptables: No chain/target/match by that name.
(exit status 1)).

Docker was installed with apt-get install docker.io apparmor and the so-called Smart Firewall is disabled. Worked fine until reboot.

2

What if you start docker manually a minute after everything else is running ? Then try to run the container ?

3

IIRC it did not work. I think it’s realetd to some firewall rules being set up on boot - but I did not investigate further at the time. My point was that if Docker (that is a common piece of sw) does not work as expected, that’s an issue worth noting.