Start network agent manually

Archive Rancher 1.x
1

Hi,

I’m currently encountering an issue where a container with a health check isn’t being marked as ‘unhealthy’ because a second host, which I believe is doing the health check monitoring, isn’t running the network agent as it hasn’t had a container start on it yet.

Is it possible to start the network agent on a host manually? Or when the host is first added?

2

Not directly, but starting a container triggers it… so you could add a service that does nothing-ish to trigger it like busybox + start once + global scale:

icanhaznetwork:
  image: busybox
  labels:
    io.rancher.scheduler.global: 'true'
    io.rancher.container.start_once: 'true'
  command:
  - /bin/true
3

Thanks, that works nicely!