-
Notifications
You must be signed in to change notification settings - Fork 47
containers do not start after reboot while dnsname enabled #19
Comments
Are these containers using static IPs, by chance? |
Thanks for the fast reply! They do not use Network:
... I also changed firewall-backend to Versions:
|
Alright, does not sound like anything I'm familiar with, then. @baude Mind taking a look? |
this should be reported as a bugzilla. please do so and let us know the number |
Bugzilla is some fine software. But which instance of bugzilla are you referring to? Do you have a URL for me? Not that I am eager to post all that a 2nd time, but if that is what it takes, fine. |
bugzilla.redhat.com |
The Error 2 may be that you have enabled both firewall and iptable at the same time. disable firewall maybe it works |
I installed dnsname and tested it successfully: A PostgreSQL container "pgsql" is found by the other container "pgclient" - just by using the container name, cool! But after reboot I get lots of problems while starting the containers again. (Problems which I do NOT get without dnsname in
/etc/cni/net.d/mynetwork.conflist
).Errors 1:
Errors 2:
Instead of just starting the container pgsql I have to remove it, recreate it, and then start it. During creation I get ...
Errors 3:
So the problems are not only lots of errors but foremost that I have to recreate the containers to get them started at all.
Environment:
Installation of dnsname:
The text was updated successfully, but these errors were encountered: