Hi there, I followed your article, and I was able to get docker to run with vmware workstation installed, but there is a strange networking issue going on.
When trying to run:
curl ----keepalive-time 5
Inside either an alpine linux, or centos linux container, I don't see the TCP keep alive packets being sent.
What is weird, is that if I run a centos VM on the same windows 10 host, and then install docker, and run the same curl command, I do see the keep alives?
Something in the way that docker-machine-windows-x86_64 creates the virtual machine prevents the docker containers from issuing keep alives.
Which VM type is being used to run docker in?
I'm assuming that it's some sort of linux vm, which should allow apps to specify socket options such as the SO_KEEPALIVE?
Any insight you might have would be greatly appreciated, thank you.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi there, I followed your article, and I was able to get docker to run with vmware workstation installed, but there is a strange networking issue going on.
When trying to run:
curl ----keepalive-time 5
Inside either an alpine linux, or centos linux container, I don't see the TCP keep alive packets being sent.
What is weird, is that if I run a centos VM on the same windows 10 host, and then install docker, and run the same curl command, I do see the keep alives?
Something in the way that docker-machine-windows-x86_64 creates the virtual machine prevents the docker containers from issuing keep alives.
Which VM type is being used to run docker in?
I'm assuming that it's some sort of linux vm, which should allow apps to specify socket options such as the SO_KEEPALIVE?
Any insight you might have would be greatly appreciated, thank you.