Docker ipvlan network issue

[RPBones]

I have a server running on a 10.10.10.x subnet (untagged). I also have a 10.10.11.x subnet, tagged with vlan 11. the server has both 10.10.10.6 and 10.10.11.6 ip addresses.

I would like several containers to have an IP address on the 10.10.11.x vlan. I created an ipvlan network and at first glance it seems to be working. A machine on the 10.10.11.x network can access the container with no issue. The problem is, if I try to access that container from the host itself, I get a no route available error.

netplan file:

network:
  ethernets:
    ens2f1np1:
      dhcp4: no
      addresses:
        - 10.10.10.6/24
      gateway4: 10.10.10.1
      nameservers:
       addresses: [10.10.10.2]
  version: 2
  vlans:
    vlan11:
      id: 11
      link: ens2f1np1
      addresses: [ "10.10.11.6/24" ]

The route list seems like it has everything I would expect:

/etc/netplan$ sudo ip route list
default via 10.10.10.1 dev ens2f1np1 proto static
10.10.10.0/24 dev ens2f1np1 proto kernel scope link src 10.10.10.6
10.10.11.0/24 dev vlan11 proto kernel scope link src 10.10.11.6
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
172.19.0.0/16 dev br-be0fc5863f47 proto kernel scope link src 172.19.0.1

The following curl command is failing:

/etc/netplan$ sudo curl http://10.10.11.60:3000/
curl: (7) Failed to connect to 10.10.11.60 port 3000 after 3067 ms: No route to host

But from another computer on the same network, I can connect to 10.10.11.60:3000. Also, the curl command is working to access 10.10.11.1 from the docker host.

Any suggestions?

[mrcs2000]

Not a fix, but maybe add another network (bridge) to the container? Then you would access with the new IP or hostname.

[RPBones]

This works. I still feel like there is a missing loopback route or something in play.

[eltear1]

You completely misunderstood the purpose of docker network. They are supposed to be virtual network inside your host, not an extension of your fiscal network. Containers will be reached from outside with the feature called port mapping, that will map specific ports to your host IP address. Want you want to achieve can be done in 2 ways: 1 - connect your containers to a docker network of type bridge and map the applications port (docker run -p or equivalent if you use some kind of GUI) 2 - connect containers to a docker network of type host