On Tue, Aug 11, Richard Brown wrote:
All of our container-systemd reference units currently start "After=network-online.target" which is also what I've been using for my own services.
Yes, we changed that in January since else no Container got ever updated. The pull request always failed as the network was not yet up and thus we always started the old container image. But maybe there is also a bug: the docu states you need additional "Wants: network-online.target". Not sure if this really helps.
If I change the znc unit to start "After=multi-user.target" the container always has the correct /etc/resolv.conf.
This implies that there is some kind of race condition with the container starting before the hosts /etc/resolv.conf is being set properly.
Maybe we need both? But I think in your case this only works by accident, multi-user.target is done late enough after network-online.target, thus everything has settled. If network-online.target is reached later than multi-user.target
I suspect this is probably a side effect of wicked being a little..inconsistant with how it informs systemd of it's readiness, but whatever the root cause, I find myself wondering if "After=network- online.target" is the best good practice for containers anyway.
I imagine multi-user.target is probably the right value if anyones wanting to run rootless containers for example..
What do you all think?
Let's fix wicked :( Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org