Olivier,
You should only need to create the /etc/mesos-slave/containerizers OR
specify --containerizers on the mesos-slave command-line. Either should
work.
- Is dockerd installed and running on the slave?
- You could be running into MESOS-1873
<https://issues.apache.org/jira/browse/MESOS-1873>. Try setting your value:
"ls -l /etc" instead of using the arguments fields with shell: false
On Tue, Oct 21, 2014 at 2:58 AM, Olivier Sallou <olivier.sal...@irisa.fr>
wrote:
> Hi,
> I try to use the default docker containizer but I can't get it work... :-(
>
> My Task is correctly executed when using default executor with CommandInfo.
>
> If I add a ContainerInfo it fails.
>
>
> I launch my slave with options: –-containerizers=docker,mesos
> (this is a source install, not system wide installed)
>
> I see in slave logs:
>
> E1021 11:50:26.392259 12748 slave.cpp:2656] Container
> '4460417c-1f78-4d99-ab07-8524c73ab35c' for executor '0' of framework
> '20141021-113729-16777343-5050-12670-0003' failed to start: None of the
> enabled containerizers (mesos) could create a container for the provided
> TaskInfo/ExecutorInfo message.
>
> and Tasks ends in FAILED state.
>
> My Task looks like:
>
> ...
> command {
> value: "ls"
> shell: false
> arguments: "-l"
> arguments: "/etc"
> }
> container {
> type: DOCKER
> docker {
> image: "docker:///dockerimages/centos-core"
> }
> }
>
>
> It acts as if the docker option on slave is not taken into account.
>
> I found on Internet that a file need to be created:
>
> echo 'docker,mesos' > /etc/mesos-slave/containerizers
>
> to activate the flag, but I do not know where this file should be
> created when mesos is not system-wide installed.
>
> Thanks
>
> Olivier
>
> --
>
>
> gpg key id: 4096R/326D8438 (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
>
>
