Coredns container fails with loop failure

1

I’ve got k3d v4.2.0

When I create a new cluster, the coredns container in the kube-system pod goes into a CrashLoopBackoff state.
Looking at the logs for that container, I see:

    .:53
    [INFO] plugin/reload: Running configuration MD5 = 442b35f70385f5c97f2491a0ce8a27f6
    CoreDNS-1.8.0
    linux/amd64, go1.15.3, 054c9ae
    [FATAL] plugin/loop: Loop (127.0.0.1:37848 -> :53) detected for zone ".", see 
    https://coredns.io/plugins/loop#troubleshooting. Query: "HINFO 
   4947423960407011533.5187313199442559305."

Any idea what’s causing this?

2

The interesting thing is that this command creates a healthy cluster where the above problem isn’t happening:

k3d cluster create cluster1

but this command causes the problem:

k3d cluster create cluster1 --volume /tmp/:/tmp/