Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

Not able to mount #2

Open
shantanuo opened this issue Mar 22, 2016 · 5 comments
Open

Not able to mount #2

shantanuo opened this issue Mar 22, 2016 · 5 comments

Comments

@shantanuo
Copy link

I am not able to mount the S3 bucket as expected. The log shows the error "operation not permitted".

[root@ip-10-45-156-16 mnt]# docker logs 3f9a77d504dc
...
2016-03-22 14:12:36,593 INFO S3 Request Payer: 'False'
2016-03-22 14:12:36,593 INFO Cache path (on disk): '/tmp/yas3fs/loffice'
2016-03-22 14:12:36,637 INFO Unique node ID: '619b33ae-ed60-48e3-a690-1d97a3cc5ea3'
fuse: failed to open /dev/fuse: Operation not permitted
2016-03-22 14:12:36,638 ERROR Uncaught Exception: <type 'exceptions.RuntimeError'> 1 <traceback object at 0x7fe398078bd8>
None

@bubenkoff
Copy link
Contributor

had you run it with --privileged

@shantanuo
Copy link
Author

Thanks. It worked with privileged. How about mentioning it on home page?

@bubenkoff
Copy link
Contributor

there's a bigger issue, the whole idea doesn't work :)
you can't export the mount for other containers!

On Wed, Mar 23, 2016 at 3:27 AM, Shantanu Oak [email protected]
wrote:

Thanks. It worked with privileged. How about mentioning it on home page?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#2 (comment)

Anatoly Bubenkov
Data Team
Innovative Travel

@shantanuo
Copy link
Author

But I can use it within the same container. Right? That is important. Dont' abandon.

@bubenkoff
Copy link
Contributor

sure you can, just hard to imagine the use-case?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants