What would be equivalent for Nomad (Docker driver) of the networking mode awsvpc
(of ECS) which allows a separate IP address for each task container?
Anyone have a job definition sample which demos this?
My use case (as of now) is “separate IP address per Docker container”
The versions I am currently am on are:
Amazon Linux 2
Consul: 1.10.1
Nomad: 1.1.2
CNI Plugins: 0.9.1
@angrycub @lgfa29
Do let me know, if any other information is required!
1 Like
After a little bit of digging, I got this:
and this …
This post courtesy of ECS Sr. Software Dev Engineer Anirudh Aithal. Today, AWS announced task networking for Amazon ECS, which enables elastic network interfaces to be attached to containers. In this post, I take a closer look at how this...
The binaries of the CNI plugins are inside the ECS Agent Docker image, which I was able to extract:
/tmp/foo/amazon-ecs-cni-plugins
$ file *
aws-appmesh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
ecs-bridge: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
ecs-eni: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
ecs-ipam: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
vpc-branch-eni: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
Though the original question remains; can Nomad directly use these (after copying to /opt/cni/
or anything equivalent would also do (something like macvlan
, etc…