[
https://issues.apache.org/jira/browse/MESOS-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744496#comment-16744496
]
Till Toenshoff commented on MESOS-9524:
---------------------------------------
After having rebooted all Windows build agent nodes Docker behaves again.
The current setup of those nodes is a bit unfortunate in that they are
long-running nodes - not ideal for a CI that runs Mesos tests - state may carry
over e.g . via kernel configuration mutations.
We will have to keep an eye on this for now. I am suggesting to use the next
instance of this problem to look deeper.
- triage this Docker problem
- evaluate if regular reboots of those nodes are a feasible kludge
> Reviewbot fails on Docker related tests.
> ----------------------------------------
>
> Key: MESOS-9524
> URL: https://issues.apache.org/jira/browse/MESOS-9524
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 1.8.0
> Reporter: Till Toenshoff
> Priority: Blocker
> Labels: ci, integration, reviewbot, windows
>
> The problem has started recently and appears to be entirely unrelated to the
> review requests being tested.
> {noformat}
> d:\dcos\mesos\mesos\src\tests\health_check_tests.cpp(2148): error:
> (docker.get()->rm(container.id, true)).failure(): Failed to run 'docker -H
> npipe:////./pipe/docker_engine rm -f -v
> 0ec7efeb0312013a7bf9af053dabb5430d1a3c34437f6fbab2349499ef563398': exited
> with status 1; stderr='Error response from daemon: container
> 0ec7efeb0312013a7bf9af053dabb5430d1a3c34437f6fbab2349499ef563398: driver
> "windowsfilter" failed to remove root filesystem: rename
> C:\ProgramData\docker\windowsfilter\0ec7efeb0312013a7bf9af053dabb5430d1a3c34437f6fbab2349499ef563398
>
> C:\ProgramData\docker\windowsfilter\0ec7efeb0312013a7bf9af053dabb5430d1a3c34437f6fbab2349499ef563398-removing:
> Access is denied.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
