Wireguard as client stack

I use the wireguard container to keep my entire stack behind a vpn. Things like qbitorrent and nzbget work fantastic through it. I have one container (threadfin) that tries to call home right at boot. Now I have all the client containers set to “depends_on:wireguard.” I think the wireguard container shows that it is up and running fine before the connection is setup. My client container (threadfin) stalls at it’s call home. I can manually reboot that particular container and it will work fine.

Is there a further way I can maybe pause client containers a bit longer before they boot and try to call home?

Self solve documented.
Under wireguard service
healthcheck:
test: [“CMD”, “curl”, “-f”, “https://ifconfig.me”]
interval: 30s
timeout: 10s
retries: 3
start_period: 30s

Under dependent containter.

healthcheck:
  test: ["CMD", "curl", "-f", "https://ifconfig.me"]
  interval: 30s
  timeout: 10s
  retries: 3
  start_period: 30s

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.