I have a go-cd deployment on top of K8s cluster that runs inside a VM (esxi vm) I configured a pipeline to build a docker image from a Dockerfile I have the Elastic agent profile configured to use gocd/gocd-agent-docker-dind:v22.3.0
While running docker build all steps pass except for a curl command that downloads a scripts from github ( I get a timeout and connection reset by peer) the same curl command does work inside the pod that runs the docker inside it and the curl work also from the VM itself and looking at the network configuration inside the agent pod I can see that my agent pod interface has mtu of 1450 (which is correct as my flannel cni sets it to 1450) while the docker interface (inside the pod ) that is used for docker containers has mtu size of 1500 that that is the problem because the inner docker container has higher mtu size that the outer pod mtu *How can I configure the MTU size for the docker daemon inside the gocd agent ?Can I build docker image by using other agent image ? maybe not a dind image ?* see this image that I found that explains the issue. https://blog.zespre.com/assets/images/dind-mtu-size-matters/the-relationship-between-two-containers.png -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/89d63d5d-e346-4e91-887c-287b66756956n%40googlegroups.com.
