Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Mon, 26 Sep 2016 06:24:20 +0000 (UTC)
From: =?utf-8?Q?St=C3=A9phane_Cottin_=28JIRA=29?= <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12959807.1461017824000.660381.1474871060564@Atlassian.JIRA>
In-Reply-To: <JIRA.12959807.1461017824000@Atlassian.JIRA>
References: <JIRA.12959807.1461017824000@Atlassian.JIRA> <JIRA.12959807.1461017824877@arcas>
Subject: [jira] [Commented] (MESOS-5229) Mesos containerizer should support
 file mounts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 26 Sep 2016 06:24:22 -0000


    [ https://issues.apache.org/jira/browse/MESOS-5229?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1552=
2203#comment-15522203 ]=20

St=C3=A9phane Cottin commented on MESOS-5229:
----------------------------------------

Even with docker (mesos container or without mesos), mounting a single file=
 is not reliable. Your file has to exists before trying to mount it, or doc=
ker will create a folder instead.

For example, if you try to mount something like /var/run/mysql/mysql.sock, =
and for some reason the docker container starts first, then you have a fold=
er created on the path and mysql cannot create its socket.

AFAIK, there is no way to tell docker to not create a folder and fail if th=
e "file" (folder, file, named pipe, socket, ...) does not exists.

If mesos containerizer file mount support is added, we should be able to ex=
plicitly describe in the proto that's "not a folder", and if we allow auto-=
creation of an empty regular file or not.

> Mesos containerizer should support file mounts
> ----------------------------------------------
>
>                 Key: MESOS-5229
>                 URL: https://issues.apache.org/jira/browse/MESOS-5229
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Joshua Cohen
>
> When using an image to represent a container's file system, it's currentl=
y not possible to mount a single file into the filesystem. I had to resort =
to adding {{RUN touch /path/to/my/file}} in my Dockerfile in order to get t=
he filesystem provisioned properly.
> It would be great if this wasn't necessary. Even better would be if Mesos=
 would create all mount points on demand, rather than requiring them to be =
present in the container filesystem (c.f. https://github.com/apache/mesos/b=
lob/master/src/slave/containerizer/mesos/isolators/filesystem/linux.cpp#L52=
2-L527)


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