Hi guys. I have a pretty vanilla setup and just one single container which fails to start @boot complaining about being unable to connect to one host's IP. Container's 'regular' unit: ... Wants=network-online.target After=network-online.target RequiresMountsFor=/run/user/2002/containers ... Restart=on-failure I think that this @boot failure - for very first user-manual restart works - is due to the fact that service/daemon to which container needs to connect, is not started soon enough & that service runs on the host. I expected 'Restart=on-failure' to take care of such circumstances but, apparently it does not, unless something else is in play here. Would you have any suggestion - all are very welcomed. many thanks, L.