Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mounting just one container #11

Open
johnlegend opened this issue Apr 14, 2011 · 29 comments
Open

Mounting just one container #11

johnlegend opened this issue Apr 14, 2011 · 29 comments

Comments

@johnlegend
Copy link

Is it possible to mount just one container. By default, cloudfuse mounts all available containers under the given account. Is it possible to specify the container name to mount as a command line parameter?

@kaysersoze
Copy link

I would also welcome this feature.

@chrishough
Copy link

Like. Like. I would also welcome this feature.

@aamirdb
Copy link

aamirdb commented Jan 16, 2012

Waiting for this feature

@flovilmart
Copy link

Hi
I just implemented this in my fork
Feel free to use it!

@jasonwbarnett
Copy link

I would really like this feature as well. I tried vfloz's fork and there is no documentation on how to mount an individual container.

@jasonwbarnett
Copy link

nevermind, i looked through vfloz's source code and found it. line 426 in https://github.com/vfloz/cloudfuse/blob/master/cloudfuse.c

container=

@flovilmart
Copy link

Hi
I updated the README when I pushed the update
You can either specify container="your container" or pass the container="parameter" in the command line!

@jasonwbarnett
Copy link

@vfloz just so you know, i tested your code and it doesn't work. it had really odd behavior. I did a 'ls' once mounted and it listed the same file multiple times.

@flovilmart
Copy link

I had no problem on my side. But I'll have a look at it.

[F v:lmart]

Le 2012-02-17 à 20:55, Jason Barnettreply@reply.github.com a écrit :

@vfloz just so you know, i tested your code and it doesn't work. it had really odd behavior. I did a 'ls' once mounted and it listed the same file multiple times.


Reply to this email directly or view it on GitHub:
#11 (comment)

@jasonwbarnett
Copy link

Just to give you more information, all of the folder structure was lost when I mounted using your version of cloudfuse. All 6100 of the items in the container where listed in the root folder.

@jasonwbarnett
Copy link

not permanently obviously... just where mounted. I'm using CentOS 5.6.

uname -a
Linux myhostname 2.6.18-274.18.1.el5xen #1 SMP Thu Feb 9 13:27:02 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

@flovilmart
Copy link

Thanks, i'll have a look, you never had a chance to list all the content in the container?
Le 2012-02-17 à 21:28, Jason Barnett a écrit :

not permanently obviously... just where mounted. I'm using CentOS 5.6.

uname -a
Linux myhostname 2.6.18-274.18.1.el5xen #1 SMP Thu Feb 9 13:27:02 EST 2012 x86_64 x86_64 x86_64 GNU/Linux


Reply to this email directly or view it on GitHub:
#11 (comment)

@jasonwbarnett
Copy link

What do you mean?

@flovilmart
Copy link

once mounted, nothing was showing with a #ls ?

Le 2012-02-17 à 21:32, Jason Barnett a écrit :

What do you mean?


Reply to this email directly or view it on GitHub:
#11 (comment)

@jasonwbarnett
Copy link

EVERYTHING showed up when i typed 'ls'

every single file at the root level showed up. there was no directory structure.

@flovilmart
Copy link

What command did you passed?

[F v:lmart]

Le 2012-02-17 à 22:36, Jason Barnettreply@reply.github.com a écrit :

EVERYTHING showed up when i typed 'ls'

every single file at the root level showed up. there was no directory structure.


Reply to this email directly or view it on GitHub:
#11 (comment)

@jasonwbarnett
Copy link

I passed the ls command

ls

@flovilmart
Copy link

I mean for mounting the container.

[F v:lmart]

Le 2012-02-27 à 10:14, Jason Barnettreply@reply.github.com a écrit :

I passed the ls command

ls


Reply to this email directly or view it on GitHub:
#11 (comment)

@jasonwbarnett
Copy link

entry in fstab:

cloudfusecontainer /media/cloudfilescontainer fuse defaults,gid=156,umask=077,allow_other,use_snet=true,username=myusername,api_key=myapikey,container=main_site 0 0

Just so you know... I renamed the binary file cloudfilescontainer

@flovilmart
Copy link

I did not test fstab integration, do you have the same behavior mounting it from command line?

[F v:lmart]

Le 2012-02-27 à 13:56, Jason Barnettreply@reply.github.com a écrit :

entry in fstab:

cloudfusecontainer /media/cloudfilescontainer fuse defaults,gid=156,umask=077,allow_other,use_snet=true,username=myusername,api_key=myapikey,container=main_site 0 0


Reply to this email directly or view it on GitHub:
#11 (comment)

@amitn322
Copy link

amitn322 commented Jun 9, 2012

Rsync has issues with the vfloz's fork of the cloud fuse. I tested with redbo's , it works except for preserve time option, but with vfloz's build , i can't seem to get rsync working. Any thoughts ?

@flovilmart
Copy link

I need to check more on the rsync. I left this project a while ago asI didn't needed it that much. On my side it all seemed to work but the performance was really bad.

@bobbymac
Copy link

This would be really useful to anyone that doesn't want to expose ALL containers. like me :-)

@renemadsen
Copy link

Is this implemented yet? If not I would really much like this feature...

@aziouk
Copy link

aziouk commented Jul 12, 2016

Hey, sorry to comment on such an old issue. I was just wondering if Cloud Fuse ever implemented single container mounting with cloud fuse?

I am thinking it might be possible to setup a complex ACL equivalent for read/write access for Cloud Files using something like S/FTP. Which would achieve complex ACL without the need for API or RBAC.

Best wishes,
Adam

@guidtz
Copy link

guidtz commented Jan 30, 2017

Hello, I have the same request to mount only one container.

Regards
Guidtz

@MrMoronIV
Copy link

7 years later, still waiting for this simple feature....

@flovilmart
Copy link

@MrMoronIV if it’s so simple, why didn’t you get a crack at it? I’m genuinely curious.

@vicomte
Copy link

vicomte commented May 1, 2020

Isn't this just using fuse subdir? Or am I misunderstanding? -o module=subdir -o subdir=/container

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

No branches or pull requests