VMs with docker do not start the firewall correctly at boot time
|Status:||Closed||Start date:||Mar 06, 2018|
|Assignee:||_InfraScience Systems Engineer||% Done:|
The existing VMs were fixed as soon as the problem arised. I just started studying a permanent solution.
A couple of possible solutions:
One of the proposals in the second thread is much easier to implement than the first one, but it's also less elegant.
- Status changed from New to In Progress
I'm implementing the following option: the docker demon will be restarted just after the iptables service. No container is going to be affected.
- % Done changed from 0 to 100
- Status changed from In Progress to Feedback
I have a fix that I'm going to test at the next service reconfiguration.
- Status changed from Feedback to Closed
Also available in: Atom