Hi team, I find myself asking the question mentioned in $SUBJ. 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. I have a simple znc IRC bouncer container based on the busybox container https://build.opensuse.org/package/show/home:RBrownSUSE:containers/znc-image using a systemd unit file similar to those in containers-systemd. It's been misbehaving lately after the VM it is hosted on restarts. The /etc/resolv.conf somehow gets populated with google DNS servers (eg. 8.8.8.8) instead of the hosts DNS servers. If I restart the container after booting, the /etc/resolv.conf in the container is correct. 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. 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? -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org