You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2017/04/14 17:30:41 UTC
[jira] [Commented] (MESOS-7081) Mesos copy backend fails on
specific docker images
[ https://issues.apache.org/jira/browse/MESOS-7081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969295#comment-15969295 ]
Gilbert Song commented on MESOS-7081:
-------------------------------------
Close this JIRA for duplication. We will land the fix soon. Please see MESOS-5028.
> Mesos copy backend fails on specific docker images
> --------------------------------------------------
>
> Key: MESOS-7081
> URL: https://issues.apache.org/jira/browse/MESOS-7081
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.1.0
> Reporter: Harpreet
>
> Filing this on behalf of a customer who reported (I will pass this along to them so that they can add more context, if needed):
> It appears that docker images doing very specific things trigger the following error:
> {noformat}
> I0207 22:25:23.212878 14465 executor.cpp:189] Version: 1.1.0
> I0207 22:25:23.338201 14464 default_executor.cpp:123] Received SUBSCRIBED event
> I0207 22:25:23.338567 14464 default_executor.cpp:127] Subscribed executor on 10.190.112.153
> I0207 22:25:23.338830 14461 default_executor.cpp:123] Received LAUNCH_GROUP event
> E0207 22:25:23.710819 14461 default_executor.cpp:366] Received '500 Internal Server Error' (Collect failed: Failed to copy layer: cp: not writing through dangling symlink '/var/lib/mesos/slave/provisioner/containers/4e6bdf2b-6a9f-4893-bbb9-8355e4863d22/containers/80a88749-8f79-4544-b7e9-185592f3593d/backends/copy/rootfses/bea1dd9d-a643-48a6-bf75-f6e9e893dbc4/bin/tar'
> ) while launching child container
> I0207 22:25:23.710849 14461 default_executor.cpp:760] Terminating after 1secs
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)