Anders Björklund

I haven't built a glibc for 13.0 (yet?), because I found that the glibc was compatible with 5.4.0 (but **not** with 4.19.x) Ubuntu 20.04 ```console $ docker run -it tinycore:13.0-x86_64...

I rebuilt glibc for 10.x, with a more conservative --enable-kernel=3.2 http://www.linuxfromscratch.org/lfs/view/stable/chapter06/glibc.html

Same story again with Tiny Core Linux 11.0 * [11.x](http://www.tinycorelinux.net/11.x/x86/release/src/toolchain/compile_tc11_x86): glibc-2.30, --enable-kernel=4.19.10

> To recompile glibc - would this be a case of having to follow the TCL build scripts - changing the glibc flag for earlier kernels - then recreating the...

* [12.x](http://www.tinycorelinux.net/12.x/x86_64/release/src/toolchain/compile_tc12_x86_64): glibc-2.32, --enable-kernel=5.4.3 * [13.x](http://www.tinycorelinux.net/13.x/x86_64/release/src/toolchain/compile_tc13_x86_64): glibc-2.34, --enable-kernel=5.4.3

Bintray went off into the sunset, so you would have to rebuild the images from source. https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

`kubernetes-cni` uses 0.8.7, which is less than 1.0.0 Currently that is sometimes leading to conflicts, with Kubic rpms. `containernetworking-plugins conflicts with kubernetes-cni` And it should still be OK with using...

Apparently a duplicate of #148, which used `winpty.exe` as a workaround * https://github.com/AlecAivazis/survey/issues/148 It was needed for "lima", for running Linux machines (also on Windows) * https://github.com/lima-vm/lima/issues/936

containerd/buildkitd doesn't even _have_ a docker socket...

You get the same bug when using other container runtimes, since the docker daemon is not running in the cluster for those. Even if you are using a custom build...