You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2018/02/08 17:29:00 UTC

[jira] [Commented] (MESOS-7685) Issue using S3FS from docker container with the mesos containerizer

    [ https://issues.apache.org/jira/browse/MESOS-7685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357255#comment-16357255 ] 

Jie Yu commented on MESOS-7685:
-------------------------------

If you are using cgroups devices isolator, /dev/fuse won't be accessible. 

> Issue using S3FS from docker container with the mesos containerizer
> -------------------------------------------------------------------
>
>                 Key: MESOS-7685
>                 URL: https://issues.apache.org/jira/browse/MESOS-7685
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, docker
>    Affects Versions: 1.1.0
>            Reporter: Andrei Filip
>            Priority: Major
>
> I have a docker image which uses S3FS to mount an amazon S3 bucket for use as a local filesystem. Playing around with this container manually, using docker, i am able to use S3FS as expected.
> When trying to use this image with the mesos containerizer, i get the following error:
> fuse: device not found, try 'modprobe fuse' first
> The way i'm launching a job that runs this s3fs command is via the aurora scheduler. Somehow it seems that docker is able to use the fuse kernel plugin, but the mesos containerizer does not.
> I've also created a stackoverflow topic about this issue here: https://stackoverflow.com/questions/44569238/using-s3fs-in-a-docker-container-ran-by-the-mesos-containerizer/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)