[ https://issues.apache.org/jira/browse/MESOS-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510107#comment-15510107 ]
Qian Zhang commented on MESOS-6215: ----------------------------------- RR: https://reviews.apache.org/r/52118/ > Add support for opaque whiteout (.wh..wh..opq) in provisioner > ------------------------------------------------------------- > > Key: MESOS-6215 > URL: https://issues.apache.org/jira/browse/MESOS-6215 > 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=192.168.122.171:5050 --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@192.168.122.171:5050 > 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 > reason: REASON_CONTAINER_LAUNCH_FAILED > {code} > Check OCI image spec for more details about opaque whiteout: > https://github.com/opencontainers/image-spec/blob/master/layer.md#opaque-whiteout -- This message was sent by Atlassian JIRA (v6.3.4#6332)