Skip to content

gateway is missing from docker inspect #6010

@pdaigle

Description

@pdaigle

#For bug reports, please include the information below:

VIC version:

Different results for release 1.1.1 and build 13118

Deployment details:

./vic-machine-linux create --target vcsa-01a.corp.local --user [email protected] --compute-resource RegionA01-COMP01 --image-store RegionA01-ISCSI01-COMP01 --volume-store RegionA01-ISCSI01-COMP01:default --public-network VM-RegionA01-vDS-COMP --container-network VM-RegionA01-vDS-COMP:routable --bridge-network Bridge02-RegionA01-vDS-COMP --name virtual-container-host-13118 --registry-ca=/etc/docker/certs.d/registry.corp.local/ca.crt --no-tls --thumbprint=F7:68:F0:93:F4:EC:B7:FE:C1:02:00:00:AB:62:1A:50:E8:9A:0E:85

Steps to reproduce:

Provision a container attached to an external container-network ("routable" in the example above) using DHCP. Gateway is not populated when displaying "docker inspect" and container is not available on the network.

docker run -d --net routable httpd

on 1.1.1:

image

on build-13118:

image

Actual behavior:

1.1.1 behaves as expected, connecting the container to the external network and the service on port 80 is reachable.

build-13118 has some missing information in docker inspect (see "Gateway" field) and the service is not available, even on the same network.

Expected behavior:

Expect same behavior between releases for container-network.

Logs:

Additional details as necessary:

I can reproduce in my lab and gather more information if needed.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions