container fails to start due to host's iface - ?
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.
Hello L., On 27.04.23 at 09:23 lejeczek via Podman wrote:
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
I would try with "Requires=" and not just "Wants=" and make sure that network-online.target is actually doing anything. Or if NetworkManager-wait-online.service (or systemd-whateveritwas for systemd-network) is the better choice in your setup. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (2)
-
Johannes Kastl -
lejeczek