You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Stavros Kontopoulos (JIRA)" <ji...@apache.org> on 2016/04/22 21:56:25 UTC

[jira] [Commented] (MESOS-4543) Mesos slave in docker fails with Mesos >= 0.25.0

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

Stavros Kontopoulos commented on MESOS-4543:
--------------------------------------------

i see the same issue and the extra parameter does not solve it see: https://issues.apache.org/jira/browse/MESOS-3793


> Mesos slave in docker fails with Mesos >= 0.25.0 
> -------------------------------------------------
>
>                 Key: MESOS-4543
>                 URL: https://issues.apache.org/jira/browse/MESOS-4543
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.25.0
>            Reporter: Giulio Eulisse
>
> I've a mesos in docker setup which works quite nicely with mesos 0.24.0. I am now trying to move to a newer mesos and I get:
> {code}
> slave_1 | + mesos-slave --master=zk://localhost:2181/mesos --work_dir=/var/lib/mesos --containerizers=docker,mesos
> slave_1 | I0128 14:00:13.759659  6904 main.cpp:185] Build: 2015-10-12 20:59:01 by root
> slave_1 | I0128 14:00:13.759711  6904 main.cpp:187] Version: 0.25.0
> slave_1 | I0128 14:00:13.759713  6904 main.cpp:190] Git tag: 0.25.0
> slave_1 | I0128 14:00:13.759716  6904 main.cpp:194] Git SHA: 2dd7f7ee115fe00b8e098b0a10762a4fa8f4600f
> slave_1 | I0128 14:00:13.864392  6904 containerizer.cpp:143] Using isolation: posix/cpu,posix/mem,filesystem/posix
> slave_1 | I0128 14:00:13.871894  6904 linux_launcher.cpp:103] Using /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
> slave_1 | I0128 14:00:13.881038  6904 systemd.cpp:128] systemd version `219` detected
> slave_1 | Failed to create a containerizer: Could not create MesosContainerizer: Failed to create launcher: Failed to initialize systemd: Failed to locate systemd runtime directory: /run/systemd/system
> {code}
> You can reproduce this by doing:
> {code}
> git clone https://github.com/ktf/ali-bot
> cd ali-bot
> docker-compose up slave
> {code}
> I think this is related to the recent changes to accomodate better integration with systemd. Any idea what I'm missing? I am running this using boot2docker.



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