Open carbocation opened 5 years ago
Hi @carbocation !
What is the use case for requesting that the same bucket be mounted twice?
I have concerns that GCSfuse is already a fragile enough solution that having a bucket mounted twice within a single dsub
task may be setting yourself up for a bad day.
Is the typical Input and Output File Handling insufficient for your use case?
Thanks.
I tried to describe the use case in the first post, but I can add more color if I did not convey the use case very well. Basically, this is not a "need," it just seems like something that should be possible and it was surprising, as a user, that it didn't work. If it's not possible, or increases risk, then no worries.
Got it. I let's leave this open and we will document that buckets should only be mounted once and that people should use --env
variables to point to specific locations inside of a mount. Should bucket mounting be the actual solution they need.
Thanks!
I'm writing a script that calls from two (potentially) different gcsfuse-mounted sources. In my testbed, they both happen to be on the same bucket, but in reality, they won't be. So, I tried to --mount the same bucket twice under different names. However, it seems that the naming is related to the bucket, rather than to the alias, so doing this fails. Maybe this is as intended, but it doesn't seem desirable.