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

mm10 example region set and mm9 example universe #79

Open
vpnagraj opened this issue Apr 23, 2018 · 9 comments
Open

mm10 example region set and mm9 example universe #79

vpnagraj opened this issue Apr 23, 2018 · 9 comments
Labels

Comments

@vpnagraj
Copy link
Collaborator

i'm seeing that the pre-loaded region set for mm10 is empty ... as is universe select list for mm9

@nsheff
Copy link
Member

nsheff commented Jul 6, 2018

there's nothing in the example folder for mm10, you're right...

but the universe for mm9 is populated.

@nsheff
Copy link
Member

nsheff commented Oct 17, 2018

I've added an example dataset now to the mm10 folder.

I'm not sure why it's not now showing up in the app, though.

@nmagee Does the container need to be rebooted (to allow the volume to be remounted) or something before it will show up in the app?

it doesn't seem like it should...

@nsheff
Copy link
Member

nsheff commented Oct 17, 2018

@vpnagraj is this possibly caused by the app loading up the file list too early?

@nmagee
Copy link
Member

nmagee commented Oct 18, 2018

Anything we drop into an already-mounted Qumulo share should be immediately visible to the container, no rebuild or reboot needed.

@nsheff
Copy link
Member

nsheff commented Oct 18, 2018

That's what I thought... but this file is there:

ls $LWREF/examples/mm10/
SE_bone_marrow.bed

but doesn't show up under mm10 on the actual app...

@nsheff nsheff added the bug label Oct 18, 2018
@nmagee
Copy link
Member

nmagee commented Oct 18, 2018 via email

@nmagee
Copy link
Member

nmagee commented Oct 18, 2018

Okay, yes -- the .bed file is visible in a newly-spawned container. So I just re-launched all LOLAweb production containers.

Let me see if Docker explains this better than I can, but as I now recall any externally mounted volume isn't truly a pass-through (internal-external) like we think of a regular NFS mount. It's actually a cached copy of the dir within the container, and Docker takes care of writing out to the share when new files are created. Unless there is some permissions issue I don't know of, it doesn't bring a "new" external file into the cached volume automatically.

@nmagee
Copy link
Member

nmagee commented Oct 18, 2018

Or I may have mounted these in a simpler, more naive way than we need. I'll research and try to make this more seamless so you can add files as you like.

https://stackoverflow.com/questions/45282608/how-to-directly-mount-nfs-share-volume-in-container-using-docker-compose-v3

@vpnagraj
Copy link
Collaborator Author

FWIW i can confirm that i'm seeing the mm10 example file now too ... and was able to execute a run with it

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

No branches or pull requests

3 participants