Vendoring in libnetwork 2da2dc055de5a474c8540871ad88a48213b0994f#13518
Vendoring in libnetwork 2da2dc055de5a474c8540871ad88a48213b0994f#13518icecrime merged 1 commit intomoby:masterfrom
Conversation
There was a problem hiding this comment.
add unit here 60 * time.Second
|
upgrading the servers ;) going to give this bad boy a spin |
There was a problem hiding this comment.
remove defer and put it at end of function
|
@mrjana what happens if docker quits before routine cleanup? |
|
@tiborvass when we come back up we cleanup the stale paths in |
|
panic in the unit-tests |
|
so running this binary on the servers and testing this pr with it, i get in like every other test-integration-cli test |
|
If GC will occur right after |
|
@LK4D4 it's not that remove by itself is a problem. It's that when we make the kernel interleave between create namespace path and remove is when this problem happens. We make sure with this fix that remove and create never interleaves |
|
LGTM |
|
🎊 |
There was a problem hiding this comment.
Yeah taking care of it :-)
|
@tiborvass @LK4D4 @vieux updated the PR taking care of the comments |
There was a problem hiding this comment.
I'm not sure it's a supported use case, but I'm pretty sure reading some people start multiple daemons on a single host, and in this case this call might be very problematic.
|
I think the cleanup logic is fine, but I'm afraid somebody, somewhere, will complain that it breaks running multiple daemon on a single host (was that @SvenDowideit?). I wish we didn't need in-memory state to manage collection, but I don't see an easy to query files to determine if they can safely be removed. LGTM with a less than 100% confidence ;-) It's already great news that you managed to workaround those kernel bugs: that unblocks 1.7.0-rc1, we can refine if the cleanup logic becomes problematic. |
|
@icecrime if the multiple daemons in a single host is a supported configuration then this could be problematic. Let me think about it a bit more. May be we can rework this a bit after 1.70-rc1? |
There was a problem hiding this comment.
could this be settable? I wonder whether --exec-root which defaults to /var/run/docker should set this
There was a problem hiding this comment.
Right now this is not settable. We can make this settable as an enhancement in the future
Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
|
So now the trade-off is that uncleanly exiting the daemon will leave dangling files behind. Not ideal, but good enough for 1.7.0? Still LGTM. |
|
LGTM |
|
It'll be improved in RC2 |
|
@icecrime but only for those container which haven't been restarted and only until a system reboot. But may be we can make it better |
|
Alright, let's do this ;-) |
Vendoring in libnetwork 2da2dc055de5a474c8540871ad88a48213b0994f
not sure if its related |
|
@tiborvass that happens when you don't have /dev/snd in your machine |
this is another one |
|
test network nat is super unstable it fails all the time for me |
Fixes #13498
Signed-off-by: Jana Radhakrishnan mrjana@docker.com