Clone hangs on kubernetes helm

Drone Support
1

I’m running a build in a drone installation in kubernetes using the stable/drone helm chart. I get this in the build output.

+ git init
Initialized empty Git repository in /drone/src/bitbucket.org/***/***/.git/
+ git remote add origin https://bitbucket.org/***/***.git
+ git fetch --no-tags origin +refs/heads/master:
fatal: unable to access 'https://bitbucket.org/***/***.git/': Operation timed out after 300013 milliseconds with 0 out of 0 bytes received
exit status 128

These are the logs that the dind container produces when the build logs are produced.

[drone-drone-agent-ccfdc8956-vxs82 drone-drone-dind] time="2018-10-08T03:19:02Z" level=warning msg="Running modprobe nf_nat failed with message: `ip: can't find device 'nf_nat'nnf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADEnnf_nat_ipv
4            16384  1 iptable_natnnf_nat                 28672  3 xt_nat,nf_nat_masquerade_ipv4,nf_nat_ipv4nnf_conntrack          106496  8 openvswitch,nf_conntrack_netlink,ip_vs,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_nat_ipv4,xt_co
nntrack,nf_natnmodprobe: can't change directory to '/lib/modules': No such file or directory`, error: exit status 1" 
[drone-drone-agent-ccfdc8956-vxs82 drone-drone-dind] time="2018-10-08T03:19:02Z" level=warning msg="Running modprobe xt_conntrack failed with message: `ip: can't find device 'xt_conntrack'nxt_conntrack           16384  8 nx_tables       
        36864 14 ipt_REJECT,xt_NFLOG,xt_statistic,xt_nat,xt_tcpudp,xt_recent,xt_set,xt_comment,xt_mark,ipt_MASQUERADE,xt_addrtype,iptable_filter,ip_tables,xt_conntracknnf_conntrack          106496  8 openvswitch,nf_conntrack_netlink,ip_v
s,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_nat_ipv4,xt_conntrack,nf_natnmodprobe: can't change directory to '/lib/modules': No such file or directory`, error: exit status 1"

my /etc/docker/daemon.json file has "iptables": true set but that didn’t seem to solve the issue.

if I kubectl exec onto the dind pod I can use wget to reach https://bitbucket.org

Any ideas on what causes this behavior?

2

drone creates a user-defined network, however, your wget test likely used the default bridge network. This behavior is typically related to user-defined networks and requires some sort of configuration change – there are a few different threads in this forum that discuss this issue, which you might be able to find if you search for Operation timed out or if you search for threads discussing user-defined networks.