You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "wangqun (JIRA)" <ji...@apache.org> on 2016/04/06 07:30:25 UTC
[jira] [Created] (MESOS-5129) Supporting Container Images in Mesos
Containerizer doesn't work
wangqun created MESOS-5129:
------------------------------
Summary: Supporting Container Images in Mesos Containerizer doesn't work
Key: MESOS-5129
URL: https://issues.apache.org/jira/browse/MESOS-5129
Project: Mesos
Issue Type: Bug
Components: build
Affects Versions: 0.29.0
Reporter: wangqun
Hi
I try to test the feature of Supporting Container Images in Mesos Containerizer according to https://github.com/apache/mesos/blob/master/docs/container-image.md#test-it-out. But it doesn't work.
I use the mesos 0.29 version.
The following is my step:
1) sudo bin/mesos-master.sh --log_dir=/var/log/mesos --ip=9.5.124.139 --work_dir=/tmp/mesos/master
2) sudo bin/mesos-slave.sh --master=9.5.124.139:5050 --ip=9.5.124.139 --hostname=mesos --isolation=docker/runtime,filesystem/linux --work_dir=/tmp/mesos/slave --log_dir=/var/log/mesos --image_providers=docker --executor_environment_variables="{}"
3)sudo src/mesos-execute --master=9.5.124.139:5050 --name=test --docker_image=library/redis --shell=false
WARNING: Logging before InitGoogleLogging() is written to STDERR
W0406 03:33:05.730432 5886 scheduler.cpp:157]
**************************************************
Scheduler driver bound to loopback interface! Cannot communicate with remote master(s). You might want to set 'LIBPROCESS_IP' environment variable to use a routable IP address.
**************************************************
I0406 03:33:05.730623 5886 scheduler.cpp:172] Version: 0.29.0
Subscribed with ID '79b6ed58-46a9-4760-a589-a28061f4f1e9-0000
task test submitted to agent 7184bc3a-243c-4ca7-8897-c98e81836ed6-S1
Received status update TASK_RUNNING for task test
4) sudo vim lt-mesos-slave.mesos.root.log.ERROR
Command 'hadoop version 2>&1' failed; this is the output:
sh: 1: hadoop: not found
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)