search

Home  >  Q&A  >  body text

docker run 的status为exited

在使用网上的docs https://github.com/yeasy/docker_practice/blob/master/mesos/installation.md

docker run --net="host" \
-p 5050:5050 \
-e "MESOS_HOSTNAME=${HOST_IP}" \
-e "MESOS_IP=${HOST_IP}" \
-e "MESOS_ZK=zk://${HOST_IP}:2181/mesos" \
-e "MESOS_PORT=5050" \
-e "MESOS_LOG_DIR=/var/log/mesos" \
-e "MESOS_QUORUM=1" \
-e "MESOS_REGISTRY=in_memory" \
-e "MESOS_WORK_DIR=/var/lib/mesos" \
-d \
garland/mesosphere-docker-mesos-master

status为exited 请问个怎么debug思路,也没有log

巴扎黑巴扎黑2771 days ago834

reply all(1)I'll reply

  • 黄舟

    黄舟2017-04-24 16:01:13

    Run steps

    1. Set the IP address of this machine
    HOST_IP=10.11.31.7
    2. Run ZooKeeper container
    docker run -d \
               -p 2181:2181 \
               -p 2888:2888 \
               -p 3888:3888 \
               garland/zookeeper
    3. Run the Mesos Master container
    docker run --net="host" \
               -p 5050:5050 \
               -e "MESOS_HOSTNAME=${HOST_IP}" \
               -e "MESOS_IP=${HOST_IP}" \
               -e "MESOS_ZK=zk://${HOST_IP}:2181/mesos" \
               -e "MESOS_PORT=5050" \
               -e "MESOS_LOG_DIR=/var/log/mesos" \
               -e "MESOS_QUORUM=1" \
               -e "MESOS_REGISTRY=in_memory" \
               -e "MESOS_WORK_DIR=/var/lib/mesos" \
               -d \
               garland/mesosphere-docker-mesos-master
    4. Run Marathon container
    docker run \
            -d \
            -p 8080:8080 \
            garland/mesosphere-docker-marathon --master zk://${HOST_IP}:2181/mesos --zk zk://${HOST_IP}:2181/marathon
    5. Run Mesos Slave container
    docker run -d \
               --name mesos_slave_1 \
               --entrypoint="mesos-slave" \
               -e "MESOS_MASTER=zk://${HOST_IP}:2181/mesos" \
               -e "MESOS_LOG_DIR=/var/log/mesos" \
               -e "MESOS_LOGGING_LEVEL=INFO" \
               garland/mesosphere-docker-mesos-master:latest

    I ran it again and there was no problem. You can view the container logs through the docker logs command to troubleshoot.

    reply
    0
  • Cancelreply