this post was submitted on 03 Nov 2024
25 points (96.3% liked)
Linux
48328 readers
555 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
fwiw: if you go w the container strategy with docker or podman, you should be able to use the storage overlay based on how i'm reading your question.
it's hard to ascertain any path forward w/o knowing more details on the cloud drive and how's it's currently mounted on the guest instance.
I have no idea how it is mounted (how can I find out?) because the binary is proprietary. This is why it is contained inside a virtual machine.
run the command
mountwith sudo access and if you can see it enumerated in the printout then you should be able to proceed with either a container overlay or separate mount point.if not, then it'll get very advanced very quickly; do you know how to use
strace?I just checked and it is mounted as a
fusedrive.A very confident NO :)
fortunately we won't have to bother w strace; but i think i can see where you'll be blocked.
do you have to provide a username/password or token when you try to access the drive now?
if yes, then you should be able to mount it like you're trying to do using instructions like these and you can use the information from the last printout to fill in the blanks.
if no, then its access is controlled outside of your guest instance and you'll need to ask your admins to enable access.
I do but it's through the proprietary GUI of the binary which has no CLI or API I can use.
then strace might help if we're lucky enough to get something like memory addresses.
strace can be very verbose and requires a lot of knowledge that i doubt i can share through comments back and forth.
is creating an intermediary like others have commented on in this post an option? they're automatically easier and faster than strace and there's no gaurantee that strace will show us the information we need.
No worries. Thank a lot nonetheless.
What do you mean by intermediary? Do you mean syncing the files with the VM and then sharing the synced copy with the host?That wouldn't work since my drive is smaller than the cloud drive and I need all the files on-demand.
that's one way. do you need them all at the same time? are they mostly the same size and type?
I need to access all files conveniently and transparently depending on what I need at work in that particular moment.
Hard no.
sshfs might work if your fuse drive is mounted with options that will let it be shared and you have sudo access to enable sshfs. also ssh access is a requirement.
how is it mounted now? it should also be in that same
mountprintout and usually at the end of the line inside parenthesis.rw,nosuid,nodev,relatime,user_id=0,group_id=0do you have sudo access and are there any rules in /etc/sudo* that match your username or any of your groups? which distribution?
Since originally writing the post I have switched to a rootless
podmancontainer. Running it how I did before (inside a VM) would simply yielduser_id=1000,group_id=1000I think.that implies that you're not using the binary anymore since you're in a container; is it using an overlay fs?
I am using the binary. Just running it inside a container instead of a VM.
Yes.
so the drive isn't mounted when the container starts; but you execute it after it started and then the drive is mounted?
Yes.
i've never seen a workflow like that so i don't think i can help you with the container.
if getting it from the host os an option, then it makes sense to see if it's possible and something like a sudoer rule or selinux could prevent that; my last question was my attempt to ascertain this.