mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Zhang (JIRA)" <>
Subject [jira] [Commented] (MESOS-6215) Add support for opaque whiteout (.wh..wh..opq) in provisioner
Date Tue, 25 Oct 2016 09:25:59 GMT


Qian Zhang commented on MESOS-6215:

Actually the solution in the patch to handle opaque whiteout
(.wh..wh..opq) is not correct, I have reworked the whole implementation to handle whiteout
files in [MESOS-6360 |], please check that
ticket for details.

> Add support for opaque whiteout (.wh..wh..opq) in provisioner
> -------------------------------------------------------------
>                 Key: MESOS-6215
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Qian Zhang
>            Assignee: Qian Zhang
>         Attachments: whiteout.diff
> In a Docker image, there can be a opaque whiteout entry (a file with the name {{.wh..wh..opq}})
under a directory which indicates all siblings under that directory should be removed. But
currently Mesos provisioner does not support to handle such opaque whiteout entry which will
cause launching container with some Docker images fails, e.g.:
> {code}
> $ sudo src/mesos-execute --master= --name=test --docker_image=rabbitmq
--command="sleep 100"
> I0921 09:22:05.167716 15522 scheduler.cpp:176] Version: 1.1.0
> I0921 09:22:05.172436 15541 scheduler.cpp:465] New master detected at master@
> Subscribed with ID 7ab88509-c068-46b3-b8be-4817e5170a7e-0000
> Submitted task 'test' to agent '7ab88509-c068-46b3-b8be-4817e5170a7e-S0'
> Received status update TASK_FAILED for task 'test'
>   message: 'Failed to launch container: Failed to remove whiteout file '/opt/mesos/provisioner/containers/2c4ed860-6256-4fa7-899b-9989d856dab7/backends/copy/rootfses/62e38280-1fd5-4fa7-8707-b19bdc24ae96/var/lib/apt/lists/partial/.wh..opq':
No such file or directory'
>   source: SOURCE_AGENT
> {code}
> Check OCI image spec for more details about opaque whiteout:

This message was sent by Atlassian JIRA

View raw message