Project

General

Profile

Actions

Task #11369

closed

VMs with docker do not start the firewall correctly at boot time

Added by Roberto Cirillo over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
System Application
Target version:
Start date:
Mar 06, 2018
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Production
Actions #2

Updated by Pasquale Pagano over 7 years ago

any news?

Actions #3

Updated by Andrea Dell'Amico over 7 years ago

The existing VMs were fixed as soon as the problem arised. I just started studying a permanent solution.

Actions #4

Updated by Andrea Dell'Amico over 7 years ago

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.

Actions #5

Updated by Andrea Dell'Amico over 7 years ago

  • 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.

Actions #6

Updated by Andrea Dell'Amico over 7 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

I have a fix that I'm going to test at the next service reconfiguration.

Actions #7

Updated by Andrea Dell'Amico over 7 years ago

  • Status changed from Feedback to Closed

Successfully tested.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)