Nomad IP range conflict

Nomad
1

Hi Folks,
I am using the Nomad client on AWS EC2 machine to run a few workloads, one very weird behavior I noticed is as below -

  • Nomad client is having docker with bridge network which has network CIDR - “172.18.0.0/16” where my EC2 machine lies in CIDR - “172.16.4.0/24”
  • My jobs are creating “bridge” network on nomad client machine where I can see few network using “192.168.128.0/20” CIDR

my questions, why is it creating bridge network in 2 CIDR spaces - “172.18.0.0/16” and “192.168.128.0/20”

2

Hey @atulsingh0

Welcome to the nomad community! Could you give an (sanitized) example of one of the jobs that’s using the separate CIDR block?