[
https://issues.apache.org/jira/browse/MESOS-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847197#comment-15847197
]
Ilya Pronin edited comment on MESOS-7034 at 1/31/17 5:45 PM:
-------------------------------------------------------------
It doesn't feel 100% right with me either. But overlay module doesn't have any
parameters so the only concern will be when it is loaded.
Also looks like Docker does the same thing though in their docs they tell that
the module should already be loaded:
https://github.com/docker/docker/blob/master/daemon/graphdriver/overlay2/overlay.go#L224
was (Author: ipronin):
It doesn't feel 100% right with me either. But "overlay" doesn't have any
parameters so the only concern will be when it is loaded.
Also looks like Docker does the same thing though in their docs they tell that
the module should already be loaded:
https://github.com/docker/docker/blob/master/daemon/graphdriver/overlay2/overlay.go#L224
> Mesos agent needs to attempt overlayfs module
> ---------------------------------------------
>
> Key: MESOS-7034
> URL: https://issues.apache.org/jira/browse/MESOS-7034
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Reporter: Santhosh Kumar Shanmugham
> Priority: Minor
>
> Mesos agent reads {{/proc/filesystems}} to check is a filesystem is
> supported. However for optional filesystems such as {{overlayfs}}, the
> modules are not loaded by default. Hence attempt to run a {{modprobe
> overlayfs}} command before reading the {{/proc/filesystems}} file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
