mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From St├ęphane Cottin (JIRA) <>
Subject [jira] [Commented] (MESOS-5229) Mesos containerizer should support file mounts
Date Mon, 26 Sep 2016 06:24:20 GMT


St├ęphane 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 docker 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 folder 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 the "file" (folder,
file, named pipe, socket, ...) does not exists.

If mesos containerizer file mount support is added, we should be able to explicitly 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:
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Joshua Cohen
> When using an image to represent a container's file system, it's currently 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 the 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

This message was sent by Atlassian JIRA

View raw message