Starting docker causes ssh to lose connection

General
1

I have an interesting issue on SLES12SP2 where I type service docker start and then I lose connection to ssh from putty… however I can ssh from Linux to Linux with no problems… Why would docker kill / prevent me from ssh?

The IP routes look good and my interface is still there… If I reboot the server ssh comes back but as soon as I start docker it kills it from putty and I have to use linux to linux.

2

Maybe your docker networks conflict with the actual networks on your host.
Start docker, ssh to it from the Linux machine, and check with “docker network ls” and “docker network inspect NETWORK-ID/NAME” to see if any of the networks have the same ip as host, if they do, you need to configure docker to use a different ip range

3

Hi Terpz, subnets are different then the host IP

4

br-76fd90 Link encap:Ethernet HWaddr 02:42:13:EE:89:32
inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

br-098837 Link encap:Ethernet HWaddr 02:42:53:5D:C8:E1
inet addr:172.19.0.1 Bcast:172.19.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

docker0 Link encap:Ethernet HWaddr 02:42:A3:7A:34:A8
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

5

after docker swarm init
docker network ls
NETWORK ID NAME DRIVER SCOPE
b62e8ad6a082 bridge bridge local
e5f5c2f138db docker_gwbridge bridge local
500f74f46b14 host host local
omk1mi736ttj ingress overlay swarm
e419dd895f4a none null local

6

you ever figure this out? i am having the same problem and cant figure it out. im about ready to delete everything and start from scratch which will be alot of work and may not even work since this is supposed to be network related. it was working one day and not the next

7

Can you tell us more about your environment? Docker can run in so many different environment It is getting harder and harder to help without knowing the exact operating system and installation method.

If it works one they and not the next day, then either your Docker network changed or something in your environment. One example is that when you are on Windows in without Docker desktop in a WSL distribution where the Docker networks’ ipranges can conflict with the ip range of WSL which changes after every reboot. It was just one possible case, so don’t focus on this one when you describe your environment :slight_smile: