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

Create named volume for available digest data #151

Open
alyssadai opened this issue May 31, 2024 · 1 comment
Open

Create named volume for available digest data #151

alyssadai opened this issue May 31, 2024 · 1 comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again

Comments

@alyssadai
Copy link
Collaborator

alyssadai commented May 31, 2024

One option could be to create a named QPN volume ahead of time, and then either manually mount it every time the container starts - or to just add a docker-compose file for this one container and define the volume in there.

Originally posted by @surchs in #150 (comment)

Example:

# get QPN data
git clone https://github.com/neurodatascience/nipoppy-qpn.git
# Make (initially empty QPN volume)
docker volume create qpn_data
# use silly-container just to copy data into the volume
docker run --rm -v qpn_data:/target -v $(PWD)/nipoppy-qpn:/source alpine cp -a /source/. /target/
# Use the volume as read-only access
docker run -d -p 8050:8050 -v qpn_data:/app/nipoppy-qpn neurobagel/digest:nightly
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
Projects
Status: No status
Development

No branches or pull requests

1 participant