Gregor Riepl

> It's not a decision. > > > There are a number of reasons to **consider** moving off of github: Let me rephrase then - I would respect your decision...

No further feedback, closing the issue.

It's unlikely that I'll be working on this further. If anybody would like to fix this themselves and submit a pull request, please go ahead.

The original question was answered. Please open a new issue if you still have problems with this firmware / device and current drivers.

That is quite far from the truth. *Most* Linux distributions have a user-writable /tmp, and in most cases, the directory has the sticky bit set, so only the user that...

Exactly the same problem here. I was using 0.10.0 before, but that crashed on startup due to #977 . #1016 was supposed to fix this - but it didn't for...

I built 0.11.0 using Go 1.11, but the segfault persists. *Edit:* It's the same with Go 1.8.7. go spits out the following messages: ``` # github.com/coreos/flannel /usr/bin/ld: /tmp/go-link-114095991/000022.o: in function...

Some more details on the involved systems: Build: Debian buster (gcc 8.2.0, glibc 2.28, go 1.11.5) Build 2: Docker build according to Makefile, tested with go 1.8.7, 1.10 and 1.11.5...

I tend to ditch the native resolver in all my Go container builds. Maybe this should also be done for flannel? Just set ```shell export CGO_ENABLED=0 ``` when compiling, and...

Are you aware of https://github.com/leblancd/kube-v6 and https://github.com/kubernetes/features/issues/508 ? I'm actually surprised that IPv6 wasn't chosen as the default networking layer for Kubernetes from the beginning. It makes a lot of...