[
https://issues.apache.org/jira/browse/MESOS-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971095#comment-15971095
]
Chun-Hung Hsiao commented on MESOS-7280:
----------------------------------------
Can you describe more about how the files are linked? Is it like that
/usr/bin/python links to some 2.6 binary in a lower layer and then it is
changed to link to some 2.7 binary in an upper layer? I'm suspecting that this
bug might be related to how symbolic links are handled in the copy backend.
> Unified containerizer provisions docker image error with COPY backend
> ---------------------------------------------------------------------
>
> Key: MESOS-7280
> URL: https://issues.apache.org/jira/browse/MESOS-7280
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
> Affects Versions: 1.0.2, 1.2.0
> Environment: CentOS 7.2，ext4, COPY
> Reporter: depay
> Assignee: Chun-Hung Hsiao
> Labels: copy-backend
>
> Error occurs on some specific docker images with COPY backend, both 1.0.2 and
> 1.2.0. It works well with OVERLAY backend on 1.2.0.
> {quote}
> I0321 09:36:07.308830 27613 paths.cpp:528] Trying to chown
> '/data/mesos/slaves/55f6df5e-2812-40a0-baf5-ce96f20677d3-S102/frameworks/20151223-150303-2677017098-5050-30032-0000/executors/ct:Transcoding_Test_114489497_1490060156172:3/runs/7e518538-7b56-4b14-a3c9-bee43c669bd7'
> to user 'root'
> I0321 09:36:07.319628 27613 slave.cpp:5703] Launching executor
> ct:Transcoding_Test_114489497_1490060156172:3 of framework
> 20151223-150303-2677017098-5050-30032-0000 with resources cpus(*):0.1;
> mem(*):32 in work directory
> '/data/mesos/slaves/55f6df5e-2812-40a0-baf5-ce96f20677d3-S102/frameworks/20151223-150303-2677017098-5050-30032-0000/executors/ct:Transcoding_Test_114489497_1490060156172:3/runs/7e518538-7b56-4b14-a3c9-bee43c669bd7'
> I0321 09:36:07.321436 27615 containerizer.cpp:781] Starting container
> '7e518538-7b56-4b14-a3c9-bee43c669bd7' for executor
> 'ct:Transcoding_Test_114489497_1490060156172:3' of framework
> '20151223-150303-2677017098-5050-30032-0000'
> I0321 09:36:37.902195 27600 provisioner.cpp:294] Provisioning image rootfs
> '/data/mesos/provisioner/containers/7e518538-7b56-4b14-a3c9-bee43c669bd7/backends/copy/rootfses/8d2f7fe8-71ff-4317-a33c-a436241a93d9'
> for container 7e518538-7b56-4b14-a3c9-bee43c669bd7
> *E0321 09:36:58.707718 27606 slave.cpp:4000] Container
> '7e518538-7b56-4b14-a3c9-bee43c669bd7' for executor
> 'ct:Transcoding_Test_114489497_1490060156172:3' of framework
> 20151223-150303-2677017098-5050-30032-0000 failed to start: Collect failed:
> Failed to copy layer: cp: cannot create regular file
> ‘/data/mesos/provisioner/containers/7e518538-7b56-4b14-a3c9-bee43c669bd7/backends/copy/rootfses/8d2f7fe8-71ff-4317-a33c-a436241a93d9/usr/bin/python’:
> Text file busy*
> I0321 09:36:58.707991 27608 containerizer.cpp:1622] Destroying container
> '7e518538-7b56-4b14-a3c9-bee43c669bd7'
> I0321 09:36:58.708468 27607 provisioner.cpp:434] Destroying container rootfs
> at
> '/data/mesos/provisioner/containers/7e518538-7b56-4b14-a3c9-bee43c669bd7/backends/copy/rootfses/8d2f7fe8-71ff-4317-a33c-a436241a93d9'
> for container 7e518538-7b56-4b14-a3c9-bee43c669bd7
> {quote}
> Docker image is a private one, so that i have to try to reproduce this bug
> with some sample Dockerfile as possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
