mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2809) Mesos fails to launch Docker images built with large Dockerfiles
Date Wed, 17 Jun 2015 07:38:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589425#comment-14589425
] 

Timothy Chen commented on MESOS-2809:
-------------------------------------

commit f13239e14f9a982465e93184ef6e34395eb561f4
Author: Timothy Chen <tnachen@gmail.com>
Date:   Sat Jun 6 19:02:21 2015 +0000

    Fix handling large docker image info on inspect.

> Mesos fails to launch Docker images built with large Dockerfiles
> ----------------------------------------------------------------
>
>                 Key: MESOS-2809
>                 URL: https://issues.apache.org/jira/browse/MESOS-2809
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 0.22.1
>            Reporter: Peter Kelley
>            Assignee: Timothy Chen
>             Fix For: 0.23.0
>
>         Attachments: Dockerfiletoolarge, Dockerfileworks
>
>
> Mesos fails to launch certain Docker images built with large Dockerfiles. When launched,
they enter the STAGING state and remain there forever. The logs don't help identify what is
going on.
> {noformat}
> I0603 18:11:03.347877 21432 slave.cpp:1144] Got assigned task brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19
for framework 20150529-174259-672272556-5050-23484-0000
> I0603 18:11:03.348214 21432 slave.cpp:1254] Launching task brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19
for framework 20150529-174259-672272556-5050-23484-0000
> I0603 18:11:03.359419 21432 slave.cpp:4208] Launching executor brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19
of framework 20150529-174259-672272556-5050-23484-0000 in work directory '/mnt/var/mesos/slaves/20150504-062547-672272556-5050-17526-S4/frameworks/20150529-174259-672272556-5050-23484-0000/executors/brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19/runs/7c6a609a-8f74-49ac-9c0e-ca1a5214bf1b'
> I0603 18:11:03.360525 21432 slave.cpp:1401] Queuing task 'brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19'
for executor brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19 of framework '20150529-174259-672272556-5050-23484-0000
> I0603 18:11:03.362375 21428 docker.cpp:626] Starting container '7c6a609a-8f74-49ac-9c0e-ca1a5214bf1b'
for task 'brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19' (and executor 'brokentestimage28.d2dece7c-0a1b-11e5-beb0-0aac5d63fb19')
of framework '20150529-174259-672272556-5050-23484-0000'
> {noformat}
> There appears to be some sort of total character limit for at least the following commands
performed in the Dockerfile MAINTAINER, LABEL, ENV, CMD (These are what I have tested against).
> This is not an actual restriction of Docker. The images launch just fine in Docker when
manually invoking docker run from a Mesos slave. 
> I have attached two Dockerfiles, one that is a single character below this limit and
works and another that is a single character above this limit and does not work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message