Docker Community Forums

Share and learn in the Docker community.

Docker with tcp md5 signature option


I’m trying to create a docker service that communicates with a remote peer over tcp with md5 option (rfc 2385 - where the tcp header digest is sent in the tcp packet and examined by the receiver to see if the current header is identical to the one in the digest).

Unfortunately since the docker container’s ip is different than the VM ip the validation fails.

What options do I have to workaround this problem (except for using host network which brings other problems with it)?