top | item 11939979

(no title)

namidark | 9 years ago

I wish they would address stability issues first, like this bug[1] that has been around 2 years and is still happening on the latest versions.

https://github.com/docker/docker/issues/5618

discuss

order

SEJeff|9 years ago

Or this nasty one[1] that has been around just over a year now. It didn't take me more work than using docker as a build server to run into this. There are some udev hacks that make it better, but the underlying issue is ultimately docker here.

Doesn't seem that docker inc upstream takes stability seriously from my standpoint.

[1] https://github.com/docker/docker/issues/13885

cpuguy83|9 years ago

Hard problems are hard. We are looking at all kinds of issues related to this, and in reality reports from that issue are likely caused by different things (some things are fixed, others obviously not).

There are several people looking how we can resolve issues like this.

cpuguy83|9 years ago

This is a caused by a race condition in the kernel that is not particularly easy to solve.

The way to solve this is not use the `--userland-proxy=false` function.

EDevil|9 years ago

Is this acknowledged by the Kernel team? Is there a ticket on the Kernel side where we can keep track of progress?