Docker: Failed to setup kubeconfig: inspect IP bridge network #8131

srehanpk · 2020-05-13T17:09:10Z

srahmed@hp:~$ minikube start
😄 minikube v1.10.1 on Ubuntu 20.04
✨ Automatically selected the docker driver
👍 Starting control plane node minikube in cluster minikube
🔥 Creating docker container (CPUs=2, Memory=2200MB) ...
🐳 Preparing Kubernetes v1.18.2 on Docker 19.03.2 ...
E0513 19:32:35.665322 20138 start.go:95] Unable to get host IP: inspect IP bridge network "de7f841a3590\n13c6d9205f9b".: docker inspect --format "{{(index .IPAM.Config 0).Gateway}}" de7f841a3590
13c6d9205f9b: exit status 1
stdout:

stderr:
Error: No such object: de7f841a3590
13c6d9205f9b

💣 failed to start node: startup failed: Failed to setup kubeconfig: inspect IP bridge network "de7f841a3590\n13c6d9205f9b".: docker inspect --format "{{(index .IPAM.Config 0).Gateway}}" de7f841a3590
13c6d9205f9b: exit status 1
stdout:

stderr:
Error: No such object: de7f841a3590
13c6d9205f9b

😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose

sharifelgamal · 2020-05-13T18:27:32Z

What docker version are you using?

sharifelgamal · 2020-05-13T18:27:56Z

@afbjorklund Would this be related to having an old docker version?

srehanpk · 2020-05-13T19:19:48Z

What docker version are you using?

Docker version 19.03.8,

srehanpk · 2020-05-13T19:20:48Z

@afbjorklund Would this be related to having an old docker version?

Docker version 19.03.8,

medyagh · 2020-05-13T19:22:36Z

@srehanpk
the error tells that the minikube container doesnt exist anymore.
are you running a system with low amount of ram?
do you mind also pasting the output of :

docker ps -a | grep minikube

and also :

docker network ls

does deleting and recreating help ?
minikube delete
minikube start --driver=docker

it worth noting I just tried it on ubuntu 20.04 and same docker version and I have no issues. and our integration tests are ubuntu and debian too and they never had this problem but I really apperciate it that you made this issue, so we can find the root cause why this happens and we prevent it for others

afbjorklund · 2020-05-13T19:45:45Z

@sharifelgamal : I don't think so, it seems to be more about the weird linebreak in the ID ?

afbjorklund · 2020-05-13T19:53:26Z

I think it is due to the filter finding two network bridges, possibly due to #8034

docker network ls --filter name=bridge --format "{{.ID}}"

 docker network create mybridge
69b9393cfa195860f9ac6d14a11e137de1acd03f83dda0c40ed3ac694f51187a
 docker network ls --filter name=bridge
NETWORK ID          NAME                DRIVER              SCOPE
6d92bb116996        bridge              bridge              local
69b9393cfa19        mybridge            bridge              local
 docker network ls --filter name=bridge --format "{{.ID}}"
6d92bb116996
69b9393cfa19

srehanpk · 2020-05-13T20:15:33Z

@srehanpk
the error tells that the minikube container doesnt exist anymore.
are you running a system with low amount of ram?
do you mind also pasting the output of :
docker ps -a | grep minikube
and also :
docker network ls
does deleting and recreating help ?
minikube delete
minikube start --driver=docker

it worth noting I just tried it on ubuntu 20.04 and same docker version and I have no issues. and our integration tests are ubuntu and debian too and they never had this problem but I really apperciate it that you made this issue, so we can find the root cause why this happens and we prevent it for others
srahmed@hp:$ docker ps -a | grep minikube
srahmed@hp:$ docker network ls
NETWORK ID NAME DRIVER SCOPE
de7f841a3590 bridge bridge local
13c6d9205f9b docker_gwbridge bridge local
ee09a402584e host host local
k8rroic09yd5 ingress overlay swarm
7c859310e263 none null local

irizzant · 2020-05-13T20:15:43Z

I'm on Ubuntu 18.04 Docker 19.03.8

$ docker network ls --filter name=bridge --format "{{.ID}}"
580ef811af7b
58a53cab81bd

Those two are absolutely normal in a docker installation, and correspond to the default bridge network plus the docker_gwbridge which is the default gateway for containers allowing them to connect to the host they run in, when node is part of a Swarm.

Starting minikube doesn't work:

minikube start --driver=docker
😄  minikube v1.10.0 on Ubuntu 18.04
✨  Using the docker driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=7900MB) ...
❗  This container is having trouble accessing https://k8s.gcr.io
💡  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
🐳  Preparing Kubernetes v1.18.1 on Docker 19.03.2 ...
E0513 22:14:50.386152    3767 start.go:95] Unable to get host IP: inspect IP bridge network "580ef811af7b\n58a53cab81bd".: docker inspect --format "{{(index .IPAM.Config 0).Gateway}}" 580ef811af7b
58a53cab81bd: exit status 1
stdout:


stderr:
Error: No such object: 580ef811af7b
58a53cab81bd

💣  failed to start node: startup failed: Failed to setup kubeconfig: inspect IP bridge network "580ef811af7b\n58a53cab81bd".: docker inspect --format "{{(index .IPAM.Config 0).Gateway}}" 580ef811af7b
58a53cab81bd: exit status 1
stdout:


stderr:
Error: No such object: 580ef811af7b
58a53cab81bd


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

But the docker container is running:

$ docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS              PORTS                                                                                                      NAMES
cf03dabc522b        gcr.io/k8s-minikube/kicbase:v0.0.10   "/usr/local/bin/entr…"   54 seconds ago      Up 50 seconds       127.0.0.1:32775->22/tcp, 127.0.0.1:32774->2376/tcp, 127.0.0.1:32773->5000/tcp, 127.0.0.1:32772->8443/tcp   minikube

Even if there is no Kubernetes at all in it:

$ docker top minikube
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                4223                4171                0                   22:14               ?                   00:00:00            /sbin/init
root                4504                4223                0                   22:14               ?                   00:00:01            /usr/local/bin/containerd
root                5267                4223                0                   22:14               ?                   00:00:00            /usr/bin/dockerd -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --default-ulimit=nofile=1048576:1048576 --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=docker --insecure-registry 10.96.0.0/12
root                4526                4223                0                   22:14               ?                   00:00:00            /usr/sbin/sshd -D
root                4379                4223                0                   22:14               ?                   00:00:00            /lib/systemd/systemd-journald

srehanpk · 2020-05-13T20:23:52Z

minikube delete
minikube start --driver=docker

These commands dose not work

srehanpk · 2020-05-13T20:26:03Z

@srehanpk
the error tells that the minikube container doesnt exist anymore.
are you running a system with low amount of ram?
do you mind also pasting the output of :
docker ps -a | grep minikube
and also :
docker network ls
does deleting and recreating help ?
minikube delete
minikube start --driver=docker

it worth noting I just tried it on ubuntu 20.04 and same docker version and I have no issues. and our integration tests are ubuntu and debian too and they never had this problem but I really apperciate it that you made this issue, so we can find the root cause why this happens and we prevent it for others

srahmed@hp:~$ docker ps -a | grep minikube
8199c44ea6a7 gcr.io/k8s-minikube/kicbase:v0.0.10 "/usr/local/bin/entr…" About a minute ago Up 56 seconds 127.0.0.1:32807->22/tcp, 127.0.0.1:32806->2376/tcp, 127.0.0.1:32805->5000/tcp, 127.0.0.1:32804->8443/tcp minikube

afbjorklund · 2020-05-13T20:29:57Z

when node is part of a Swarm

I think this was the untested bit, I don't think we have any tests with both Swarm and Kubernetes...

Anyway, most likely the code was meant only to hit the default "bridge" and not the docker_gwbridge
It was just an error, due to the word bridge appearing in both networks. The mentioned PR will fix.

afbjorklund · 2020-05-13T20:35:29Z

Here is some more information about docker_gwbridge:

https://docs.docker.com/network/overlay/

When you initialize a swarm or join a Docker host to an existing swarm, two new networks are created on that Docker host:

an overlay network called `ingress`, which handles control and data traffic related to swarm services. When you create a swarm service and do not connect it to a user-defined overlay network, it connects to the ingress network by default.
a bridge network called `docker_gwbridge`, which connects the individual Docker daemon to the other daemons participating in the swarm.

I do think that Swarm must have been enabled manually ?

irizzant · 2020-05-13T21:05:51Z

It's simply enabled with:
docker swarm init
on a host, in my case it's a single node Swarm.
Having a Swarm in a host makes multiple bridge network being used anyway.

medyagh · 2020-05-13T23:17:48Z

this seems to be a bug and we could do a better job in finding the correct bridge

medyagh · 2020-05-13T23:19:32Z

@afbjorklund I wonder if we still need to warn the user to disable swarm ? even if we detect the bridge correctly

afbjorklund · 2020-05-14T06:19:12Z

@medyagh : no idea, I haven't tried to mix Kubernetes and Docker Swarm myself
But I thought that e.g. Docker Desktop has both of them installed, out-of-the-box

So we probably shouldn't worry about swarm, but to get the minikube code working ?
Current code breaks the same way, if you add "mybridge" or "bridge2" or anything...

medyagh · 2020-08-19T21:58:50Z

@srehanpk on latest minikube I tried enabling swarm on mac and I have no issues, do we still have this issue ?

kadern0 · 2020-08-19T22:23:10Z

With latest code, if you try this, it will fail:

docker network create testing_bridge

docker network list
NETWORK ID          NAME                DRIVER              SCOPE
ddb969f50f43        bridge              bridge              local
089b251a4b6a        host                host                local
442c7ccfda68        none                null                local
24546dec8368        testing_bridge      bridge              local

./out/minikube start --memory 2048 --cpus 2 -p testing2
😄  [testing2] minikube v1.12.3 on Ubuntu 20.04
✨  Automatically selected the docker driver. Other choices: kvm2, virtualbox
👍  Starting control plane node testing2 in cluster testing2
🔥  Creating docker container (CPUs=2, Memory=2048MB) ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
E0820 08:17:07.515986  314891 start.go:97] Unable to get host IP: inspect IP bridge network "ddb969f50f43\n24546dec8368".: docker network inspect --format "{{(index .IPAM.Config 0).Gateway}}" ddb969f50f43
24546dec8368: exit status 1
stdout:


stderr:
Error: No such network: ddb969f50f43
24546dec8368

💣  failed to start node: startup failed: Failed to setup kubeconfig: inspect IP bridge network "ddb969f50f43\n24546dec8368".: docker network inspect --format "{{(index .IPAM.Config 0).Gateway}}" ddb969f50f43
24546dec8368: exit status 1
stdout:


stderr:
Error: No such network: ddb969f50f43
24546dec8368


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

I don't think many users will run into this, but the way minikube is filtering the networks is prone to failure, it will pick all networks containing "bridge" and mix them in a string with new line characters and then it will fail.

medyagh · 2020-08-19T22:28:02Z

here I tried on ubuntu as well

jenkins@instance-1:~$ docker swarm init
Swarm initialized: current node (vik7ym1zk79kxr44egvlldfnv) is now a manager.

To add a worker to this swarm, run the following command:

    docker swarm join --token ****

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

jenkins@instance-1:~$ docker info | grep Swa
 Swarm: active
WARNING: No swap limit support
jenkins@instance-1:~$ ./minikube-linux-amd64 start 
😄  minikube v1.12.3 on Ubuntu 20.04
✨  Automatically selected the docker driver
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=2200MB) ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"
💗  Kubectl not found in your path
👉  You can use kubectl inside minikube. For more information, visit https://minikube.sigs.k8s.io/docs/handbook/kubectl/
💡  For best results, install kubectl: https://kubernetes.io/docs/tasks/tools/install-kubectl/

kadern0 · 2020-08-19T22:39:04Z

I was looking into this from this issue's perspective #8274 (that I closed in favor of this one because the underlying cause is the same).

medyagh · 2020-08-19T22:43:28Z

can you replicate this issue ? @kadern0

kadern0 · 2020-08-19T22:56:53Z

Yes, just put you the steps to replicate the issue two comments above using the latest code. (Just create a docker network containing "bridge" before starting minikube)

medyagh · 2020-08-20T18:11:41Z

@kadern0 I couldn't reproduce on mac


medya@~ $ docker network create bridge-1
241bbcbecb087d0a05188c9b910f735ceeff301d3310b816440c77d2cd6d4763
medya@~ $ minikube version
minikube version: v1.12.3
commit: 2243b4b97c131e3244c5f014faedca0d846599f5-dirty
medya@~ $ minikube delete --all
🔥  Deleting "minikube" in docker ...
🔥  Removing /Users/medya/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.
🔥  Successfully deleted all profiles
medya@~ $ minikube start
😄  minikube v1.12.3 on Darwin 10.15.6
✨  Automatically selected the docker driver. Other choices: hyperkit, virtualbox
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=2948MB) ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube

medyagh · 2020-08-20T18:15:18Z

medya@~ $ docker network create testing_bridge
bdb3812f8ab7d7d5bbcb78dbb9e5336e9456fbaf82d4af118494188b5886e8ac


medya@~ $ minikube start
😄  minikube v1.12.3 on Darwin 10.15.6
✨  Automatically selected the docker driver. Other choices: hyperkit, virtualbox
❗  Your system has 16384MB memory but Docker has only 2996MB. For a better performance increase to at least 3GB.
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=2948MB) ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"


medya@~ $ docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
2e2f5269fbdf        bridge              bridge              local
241bbcbecb08        bridge-1            bridge              local
6ceabcdd0b73        docker_gwbridge     bridge              local
7493d3908b3b        host                host                local
cnqffuv1zryx        ingress             overlay             swarm
32dd48b9b3da        minikube            bridge              local
de4265f5379d        none                null                local
bdb3812f8ab7        testing_bridge      bridge              local

kadern0 · 2020-08-20T23:21:19Z

$ minikube version
minikube version: v1.12.3
commit: 2243b4b97c131e3244c5f014faedca0d846599f5-dirty

Cleaning up and fresh start

pcaderno@pcaderno-desktop$ minikube delete --all
🔥  Deleting "minikube" in docker ...
🔥  Removing /home/pcaderno/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.
🔥  Successfully deleted all profiles
pcaderno@pcaderno-desktop$ minikube start 
😄  minikube v1.12.3 on Ubuntu 19.10
✨  Automatically selected the docker driver
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=7800MB) ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"

All good, now let's break it

pcaderno@pcaderno-desktop$ minikube stop
✋  Stopping node "minikube"  ...
🛑  Powering off "minikube" via SSH ...
🛑  1 nodes stopped.

pcaderno@pcaderno-desktop$ docker network create testing_bridge
8622100c89c5e6ed0f4fb957a9117a3bfe85f53aac5de40ec7e74b4c9af9b8ac

pcaderno@pcaderno-desktop$ minikube start
😄  minikube v1.12.3 on Ubuntu 19.10
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing docker container for "minikube" ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
E0821 09:11:33.527143    4903 start.go:97] Unable to get host IP: inspect IP bridge network "f631e95f4100\n8622100c89c5".: docker network inspect --format "{{(index .IPAM.Config 0).Gateway}}" f631e95f4100
8622100c89c5: exit status 1
stdout:


stderr:
Error: No such network: f631e95f4100
8622100c89c5

💣  failed to start node: startup failed: Failed to setup kubeconfig: inspect IP bridge network "f631e95f4100\n8622100c89c5".: docker network inspect --format "{{(index .IPAM.Config 0).Gateway}}" f631e95f4100
8622100c89c5: exit status 1
stdout:


stderr:
Error: No such network: f631e95f4100
8622100c89c5


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

List docker networks

pcaderno@pcaderno-desktop$ docker network ls
NETWORK ID          NAME                 DRIVER              SCOPE
f631e95f4100        bridge               bridge              local
meiftgx9pkqf        devdocs-server-net   overlay             swarm
db34ce28a755        host                 host                local
9mxl3y16ro30        ingress              overlay             swarm
e945b60808c9        none                 null                local
8622100c89c5        testing_bridge       bridge              local

Delete testing network and start minikube

pcaderno@pcaderno-desktop$ docker network rm testing_bridge
testing_bridge
pcaderno@pcaderno-desktop$ minikube start
😄  minikube v1.12.3 on Ubuntu 19.10
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🏃  Updating the running docker "minikube" container ...
🐳  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube"

It works fine again. Do you have a linux box available for testing?

davidshen84 · 2020-08-30T00:58:43Z

Hi,

I think I am hit by this issue as well. I am on Gentoo distro. I think the docker_gwbridge on my system is created by docker, so I don't think I can just delete it. Is there's a walkaround/fix to this issue?

NETWORK ID          NAME                DRIVER              SCOPE
83eca32b5df3        bridge              bridge              local
0f6b47c0882d        docker_gwbridge     bridge              local
21d9995cf792        host                host                local
tgv0ut9u3sgw        ingress             overlay             swarm
8ab892bf9aac        none                null                local

Client:
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.14.7
 Git commit:        48a66213fe
 Built:             Sat Aug  8 06:09:21 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.14.7
  Git commit:       48a66213fe
  Built:            Sat Aug  8 06:08:46 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        35bd7a5f69c13e1563af8a93431411cd9ecf5021
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683b971d9c3ef73f284f176672c44b448662

minikube version: v1.11.0
commit: 57e2f55f47effe9ce396cea42a1e0eb4f611ebbd

kadern0 · 2020-08-30T22:50:13Z

@davidshen84 the PR that will close this issue is this one -> #9094 if you need a quick temporary fix, you can always use my code from here -> #9062

davidshen84 · 2020-08-31T12:24:25Z

Thanks Pablo!

…

On Mon, Aug 31, 2020, 08:50 Pablo Caderno ***@***.***> wrote: @davidshen84 <https://github.com/davidshen84> the PR that will close this issue is this one -> #9094 <#9094> if you need a quick temporary fix, you can always use my code from here -> #9062 <#9062> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8131 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQBTOTYXIVORWK3O7W6UTSDLJTDANCNFSM4M76RZLQ> .

tstromberg · 2020-09-01T23:47:33Z

Fixed by #9062

tstromberg · 2020-09-02T17:21:19Z

I'm going to leave this open until the v1.13 release as so many people are running into it. As a workaround until the release later this week, you should be able to use minikube from head (or delete the bridge network):

https://storage.googleapis.com/minikube-builds/9160/minikube-darwin-amd64
https://storage.googleapis.com/minikube-builds/9160/minikube-linux-amd64
https://storage.googleapis.com/minikube-builds/9160/minikube-windows-amd64.exe

If this updated build does not help, please let us know immediately so that we can fix it before the release.

RoSk0 · 2020-09-06T23:15:43Z

Upgrading to v1.13.0 fixed the issue for me (was using 1.12.3).

Thanks!

tstromberg · 2020-09-08T16:30:33Z

@RoSk0 - thank you for the confirmation that minikube v1.13.0 fixes the issue!

mythreyi1905 · 2020-10-11T03:54:41Z

Upgrading to v1.13.0 fixed the issue for me (was using 1.12.3).

Thanks!

This works !!! I had docker swarm initialized and even when I disabled it followed by deleting of .docker/config.json file, I kept encountering the same error. Upgrading minikube works. Thanks @RoSk0

sharifelgamal added co/docker-driver Issues related to kubernetes in container priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels May 13, 2020

medyagh mentioned this issue May 13, 2020

Minikube crashes on start #8122

Closed

medyagh added the kind/bug Categorizes issue or PR as related to a bug. label May 13, 2020

afbjorklund mentioned this issue May 13, 2020

wip: Use regex anchors to be sure we get bridge from the docker network inspect command #8034

Closed

afbjorklund changed the title ~~minikube installation issue in ubuntu 20.4~~ minikube installation issue in ubuntu 20.4 with docker swarm May 13, 2020

afbjorklund mentioned this issue May 13, 2020

minikube installation problum on ubuntu 20.4 #8142

Closed

medyagh modified the milestones: v.1.12.0, v1.11.0 May28 May 13, 2020

medyagh changed the title ~~minikube installation issue in ubuntu 20.4 with docker swarm~~ docker driver fail to get network bridge when Swarm is enabled May 13, 2020

medyagh added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels May 13, 2020

afbjorklund mentioned this issue Aug 25, 2020

centos7 minikube start error #9076

Closed

kadern0 mentioned this issue Aug 30, 2020

Failed to setup kubeconfig: inspect IP bridge network "f990f7a561a9\n2125d74f1c6f #9123

Closed

tstromberg changed the title ~~docker driver fail to get network bridge when Swarm is enabled~~ Docker: Failed to setup kubeconfig: inspect IP bridge network (if additional bridge exists, such as Swarm) Sep 1, 2020

tstromberg closed this as completed Sep 1, 2020

tstromberg changed the title ~~Docker: Failed to setup kubeconfig: inspect IP bridge network (if additional bridge exists, such as Swarm)~~ Docker: Failed to setup kubeconfig: inspect IP bridge network Sep 2, 2020

tstromberg reopened this Sep 2, 2020

tstromberg added the top-10-issues Top 10 support issues label Sep 2, 2020

tstromberg mentioned this issue Sep 2, 2020

Unable to get host IP: inspect IP bridge network #9153

Closed

tstromberg removed this from the v1.13.0 milestone Sep 2, 2020

tstromberg mentioned this issue Sep 2, 2020

Failed to setup kubeconfig: inspect IP bridge network: No such network: xxx #9041

Closed

tstromberg closed this as completed Sep 8, 2020

mythreyi1905 mentioned this issue Oct 11, 2020

docker driver: IPs output should only be one line, got 2 lines #8603

Closed

kadern0 mentioned this issue Nov 13, 2020

Error: No such network: 56bcceb8c923 #9644

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker: Failed to setup kubeconfig: inspect IP bridge network #8131

Docker: Failed to setup kubeconfig: inspect IP bridge network #8131

srehanpk commented May 13, 2020

sharifelgamal commented May 13, 2020

sharifelgamal commented May 13, 2020

srehanpk commented May 13, 2020

srehanpk commented May 13, 2020

medyagh commented May 13, 2020 •

edited

Loading

afbjorklund commented May 13, 2020

afbjorklund commented May 13, 2020 •

edited

Loading

srehanpk commented May 13, 2020

irizzant commented May 13, 2020 •

edited

Loading

srehanpk commented May 13, 2020

srehanpk commented May 13, 2020

afbjorklund commented May 13, 2020

afbjorklund commented May 13, 2020

irizzant commented May 13, 2020

medyagh commented May 13, 2020

medyagh commented May 13, 2020

afbjorklund commented May 14, 2020 •

edited

Loading

medyagh commented Aug 19, 2020

kadern0 commented Aug 19, 2020

medyagh commented Aug 19, 2020 •

edited

Loading

kadern0 commented Aug 19, 2020

medyagh commented Aug 19, 2020

kadern0 commented Aug 19, 2020

medyagh commented Aug 20, 2020 •

edited

Loading

medyagh commented Aug 20, 2020

kadern0 commented Aug 20, 2020

davidshen84 commented Aug 30, 2020

kadern0 commented Aug 30, 2020

davidshen84 commented Aug 31, 2020 via email

tstromberg commented Sep 1, 2020

tstromberg commented Sep 2, 2020

RoSk0 commented Sep 6, 2020

tstromberg commented Sep 8, 2020 •

edited

Loading

mythreyi1905 commented Oct 11, 2020

Docker: Failed to setup kubeconfig: inspect IP bridge network #8131

Docker: Failed to setup kubeconfig: inspect IP bridge network #8131

Comments

srehanpk commented May 13, 2020

sharifelgamal commented May 13, 2020

sharifelgamal commented May 13, 2020

srehanpk commented May 13, 2020

srehanpk commented May 13, 2020

medyagh commented May 13, 2020 • edited Loading

afbjorklund commented May 13, 2020

afbjorklund commented May 13, 2020 • edited Loading

srehanpk commented May 13, 2020

irizzant commented May 13, 2020 • edited Loading

srehanpk commented May 13, 2020

srehanpk commented May 13, 2020

afbjorklund commented May 13, 2020

afbjorklund commented May 13, 2020

irizzant commented May 13, 2020

medyagh commented May 13, 2020

medyagh commented May 13, 2020

afbjorklund commented May 14, 2020 • edited Loading

medyagh commented Aug 19, 2020

kadern0 commented Aug 19, 2020

medyagh commented Aug 19, 2020 • edited Loading

kadern0 commented Aug 19, 2020

medyagh commented Aug 19, 2020

kadern0 commented Aug 19, 2020

medyagh commented Aug 20, 2020 • edited Loading

medyagh commented Aug 20, 2020

kadern0 commented Aug 20, 2020

davidshen84 commented Aug 30, 2020

kadern0 commented Aug 30, 2020

davidshen84 commented Aug 31, 2020 via email

tstromberg commented Sep 1, 2020

tstromberg commented Sep 2, 2020

RoSk0 commented Sep 6, 2020

tstromberg commented Sep 8, 2020 • edited Loading

mythreyi1905 commented Oct 11, 2020

medyagh commented May 13, 2020 •

edited

Loading

afbjorklund commented May 13, 2020 •

edited

Loading

irizzant commented May 13, 2020 •

edited

Loading

afbjorklund commented May 14, 2020 •

edited

Loading

medyagh commented Aug 19, 2020 •

edited

Loading

medyagh commented Aug 20, 2020 •

edited

Loading

tstromberg commented Sep 8, 2020 •

edited

Loading