[
https://issues.apache.org/jira/browse/MESOS-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626356#comment-15626356
]
Mischa Krüger edited comment on MESOS-6518 at 11/1/16 7:04 PM:
---------------------------------------------------------------
I'm using DC/OS to deploy a service. In my case I'm using a docker image to
spawn a flink instance:
https://github.com/Makman2/dcos-flink-docker/blob/d754767152e44ad81bff890ced9fba97d5ffd99c/Dockerfile
Also I'm using a custom command, in this case it contains the same `ln` command
like in the Dockerfile:
{code}
echo "--------------------------------";
ls $MESOS_SANDBOX;
echo "--------------------------------";
ln -s $(pwd)/mesos_sandbox/* $MESOS_SANDBOX/;
echo "ln -s $(pwd)/mesos_sandbox/* $MESOS_SANDBOX/";
ls $MESOS_SANDBOX;
sleep 60;
{code}
which write following into the stdout file:
{code}
--container="mesos-90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0.4515a673-3baa-4af3-83b7-b0755fe4ad94"
--docker="docker" --docker_socket="/var/run/docker.sock" --help="false"
--initialize_driver_logging="true"
--launcher_dir="/opt/mesosphere/packages/mesos--55e36b7783f1549d26b7567b11090ff93b89487a/libexec/mesos"
--logbufsecs="0" --logging_level="INFO"
--mapped_directory="/mnt/mesos/sandbox" --quiet="false"
--sandbox_directory="/var/lib/mesos/slave/slaves/90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0/frameworks/90e534a9-de1b-4a32-ac01-d7d9d54337f2-0000/executors/container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1/runs/4515a673-3baa-4af3-83b7-b0755fe4ad94"
--stop_timeout="20secs"
--container="mesos-90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0.4515a673-3baa-4af3-83b7-b0755fe4ad94"
--docker="docker" --docker_socket="/var/run/docker.sock" --help="false"
--initialize_driver_logging="true"
--launcher_dir="/opt/mesosphere/packages/mesos--55e36b7783f1549d26b7567b11090ff93b89487a/libexec/mesos"
--logbufsecs="0" --logging_level="INFO"
--mapped_directory="/mnt/mesos/sandbox" --quiet="false"
--sandbox_directory="/var/lib/mesos/slave/slaves/90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0/frameworks/90e534a9-de1b-4a32-ac01-d7d9d54337f2-0000/executors/container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1/runs/4515a673-3baa-4af3-83b7-b0755fe4ad94"
--stop_timeout="20secs"
Registered docker executor on 10.0.2.185
Starting task container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1
--------------------------------
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
--------------------------------
ln -s /flink-1.2-SNAPSHOT/mesos_sandbox/* /mnt/mesos/sandbox/
flink-conf.yaml
flink-python_2.10-1.2-SNAPSHOT.jar
flink.jar
log4j-1.2.17.jar
log4j.properties
slf4j-log4j12-1.7.7.jar
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
{code}
But only following files are displayed in the sandbox view:
{code}
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
{code}
so like no linking ever happened. But as you see in the stdout file, the links
are there! :/
PS:
When I try to spawn a service with following command:
{code}
touch x.txt;
ln -s x.txt my-symlink;
{code}
I can indeed see the symlink appearing in the sandbox view. Very strange...
was (Author: makman2):
I'm using DC/OS to deploy a service. In my case I'm using a docker image to
spawn a flink instance:
https://github.com/Makman2/dcos-flink-docker/blob/d754767152e44ad81bff890ced9fba97d5ffd99c/Dockerfile
Also I'm using a custom command, in this case it contains the same `ln` command
like in the Dockerfile:
{code}
echo "--------------------------------";
ls $MESOS_SANDBOX;
echo "--------------------------------";
ln -s $(pwd)/mesos_sandbox/* $MESOS_SANDBOX/;
echo "ln -s $(pwd)/mesos_sandbox/* $MESOS_SANDBOX/";
ls $MESOS_SANDBOX;
sleep 60;
{code}
which write following into the stdout file:
{code}
--container="mesos-90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0.4515a673-3baa-4af3-83b7-b0755fe4ad94"
--docker="docker" --docker_socket="/var/run/docker.sock" --help="false"
--initialize_driver_logging="true"
--launcher_dir="/opt/mesosphere/packages/mesos--55e36b7783f1549d26b7567b11090ff93b89487a/libexec/mesos"
--logbufsecs="0" --logging_level="INFO"
--mapped_directory="/mnt/mesos/sandbox" --quiet="false"
--sandbox_directory="/var/lib/mesos/slave/slaves/90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0/frameworks/90e534a9-de1b-4a32-ac01-d7d9d54337f2-0000/executors/container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1/runs/4515a673-3baa-4af3-83b7-b0755fe4ad94"
--stop_timeout="20secs"
--container="mesos-90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0.4515a673-3baa-4af3-83b7-b0755fe4ad94"
--docker="docker" --docker_socket="/var/run/docker.sock" --help="false"
--initialize_driver_logging="true"
--launcher_dir="/opt/mesosphere/packages/mesos--55e36b7783f1549d26b7567b11090ff93b89487a/libexec/mesos"
--logbufsecs="0" --logging_level="INFO"
--mapped_directory="/mnt/mesos/sandbox" --quiet="false"
--sandbox_directory="/var/lib/mesos/slave/slaves/90e534a9-de1b-4a32-ac01-d7d9d54337f2-S0/frameworks/90e534a9-de1b-4a32-ac01-d7d9d54337f2-0000/executors/container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1/runs/4515a673-3baa-4af3-83b7-b0755fe4ad94"
--stop_timeout="20secs"
Registered docker executor on 10.0.2.185
--------------------------------
Starting task container-test.24183a01-a064-11e6-a8e8-9278bb0b38e1
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
--------------------------------
ln -s /flink-1.2-SNAPSHOT/mesos_sandbox/* /mnt/mesos/sandbox/
flink-conf.yaml
flink-python_2.10-1.2-SNAPSHOT.jar
flink.jar
log4j-1.2.17.jar
log4j.properties
slf4j-log4j12-1.7.7.jar
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
{code}
But only following files are displayed in the sandbox view:
{code}
stderr
stderr.logrotate.conf
stdout
stdout.logrotate.conf
{code}
so like no linking ever happened. But as you see in the stdout file, the links
are there! :/
PS:
When I try to spawn a service with following command:
{code}
touch x.txt;
ln -s x.txt my-symlink;
{code}
I can indeed see the symlink appearing in the sandbox view. Very strange...
> Mesos dashboard: Symlinks not displayed in sandbox view
> -------------------------------------------------------
>
> Key: MESOS-6518
> URL: https://issues.apache.org/jira/browse/MESOS-6518
> Project: Mesos
> Issue Type: Improvement
> Components: webui
> Reporter: Mischa Krüger
> Assignee: haosdent
> Priority: Minor
> Attachments: sandbox.png, tmp.png
>
>
> Soft symbolic links do not appear in the sandbox, though they exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
