Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): docker-1.9.1-19.el7.x86_64 docker version: 1.9.1 Image full_name:registry.access.redhat.com/rhel7/rhel:latest LONG_ID:bf63a676257aeb7a75a6bbbda138398bbaf223ab34fe9d169e458f9b399004ef How reproducible: Unknown, failure found in CI: https://url.corp.redhat.com/acc530c with job configuration: https://url.corp.redhat.com/e7afa6c Steps to Reproduce: 1. run docker inspect against a running container Actual results: [ { ...cut... "NetworkSettings": { ...cut... "Networks": { "bridge": { <----- lower-case B ...cut... } ] Expected results: [ { ...cut... "NetworkSettings": { ...cut... "Networks": { "Bridge": { <----- upper-case B ...cut... } ] Additional info:
I don't see this as a bug. "bridge" is the name of the network. It could just as easily been called "foobar". man docker run ... --net="bridge" Set the Network mode for the container 'bridge': create a network stack on the default Docker bridge 'none': no networking 'container:<name|id>': reuse another container's network stack 'host': use the Docker host network stack. Note: the host mode gives the container full access to local system services such as D-bus and is therefore considered insecure. '<network-name>|<network-id>': connect to a user-defined network
(In reply to Daniel Walsh from comment #2) > I don't see this as a bug. "bridge" is the name of the network. It could > just as easily been called "foobar". Oh ok, so it's more of a 'data' key as opposed structural. Fair enough, I'll add an exception to checking this in CI.
(ref: https://github.com/autotest/autotest-docker/pull/585 )