Nomad IP range conflict

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 - “” where my EC2 machine lies in CIDR - “”
  • My jobs are creating “bridge” network on nomad client machine where I can see few network using “” CIDR

my questions, why is it creating bridge network in 2 CIDR spaces - “” and “”

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?