coredns doesn't start due to missing glibc

[Bezineb]

Hi,

I've tried to follow the procedure, however the coredns-plugin docker image would start because of the following:
/ # file ./coredns
./coredns: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, Go BuildID=B38ftmGPbkw-eOi2C8h6/UvtajEJHGZO4nxrOLX15/4p_boMij3Nd4NA8WfimV/0DIjNgv-qLC2hmcRLRN5, BuildID[sha1]=3bb93972be17fa0339ab81322fdde54b5b2d2195, not stripped

As the docker image is build from "scratch", it cannot have this dependency. I've changed it to use alpine + libc6-compat.

Did you face the same issue?

Thanks!

[Dovy Bartkevicius]

@Bezineb thanks for opening the issue. I've pushed a fix in #18

[shreya-bhatnagar]

@dovys @Bezineb @boffbowsh : @lazywhite : Hey my coredns and egress-operator-deployment pods are running fine now. But egress-operator-controller-manager pod (created after make deploy IMG=my_azure_repo/egress-operator:v0.1 ) is giving error in pod description as:

 Failed   m2s (x4 over 4m35s)   kubelet  Error: failed to create containerd task: 
 OCI runtime create failed: container_linux.go:380: starting container process 
 caused: exec: "/manager": stat /manager: no such file or directory: unknown

my make run and make deploy IMG=my_azure_repo/egress-operator:v0.1 also worked fine without any error.

You have any idea why is it so ? some path /manager not able to be recognized by makefile it seems?