nomad-driver-containerd
nomad-driver-containerd copied to clipboard
there is no ip address in the lo network
there is no ip address(127.0.0.1/8
) in the lo network, so app can not listen on 127.0.0.1
root@bypass-route:/# ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 2e:f4:d0:00:17:83 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.26.64.2/20 brd 172.26.79.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::2cf4:d0ff:fe00:1783/64 scope link
valid_lft forever preferred_lft forever
when change to docker driver, the lo network is fine.
root@9b68f72d354e:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
3: eth0@if118: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 32:2c:db:6a:dc:f0 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.26.64.107/20 brd 172.26.79.255 scope global eth0
valid_lft forever preferred_lft forever
the job file:
job "test2" {
datacenters = ["dc1"]
group "test2" {
network {
mode = "bridge"
}
task "test2" {
driver = "containerd-driver"
config {
image = "docker.io/library/ubuntu:20.04"
command = "sleep"
args = ["600s"]
}
resources {
cpu = 500
memory = 256
}
}
}
}
Is there any suggestion here?
thanks.
@lisongmin hashicorp/nomad
is probably a better place for this issue.
When you set
network {
mode = "bridge"
}
nomad
sets up the bridge by relying on the CNI bridge plugin. containerd-driver
just joins the network namespace
set up by nomad
.
I think hashicorp/nomad
would be a good place to start the discussion. Can you open the issue there?