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

Location of dependent containers during run #733

Closed
pagrubel opened this issue Oct 24, 2023 · 2 comments
Closed

Location of dependent containers during run #733

pagrubel opened this issue Oct 24, 2023 · 2 comments
Labels

Comments

@pagrubel
Copy link
Collaborator

Should the images be in the bee_workdir or /tmp or some other temporary directory. Now we have several locations for dependent containers all in <bee_workdir>. We should evaluate if this is what we should be doing. In the past, for Charliecloud it was suggested that they should in a temporary directory, most likely due to the delay in using NFS.

@pagrubel
Copy link
Collaborator Author

We are using redis and neo4j dependencies in containers. The neo4j container is untarred into <bee_workdir>/deps/dependent_container and redis is untarrred to <bee_workdir>/redis_container. I propose that we untar them both into: <bee_workdir>/dependant_containers and name the neo4j container "neo4j_container". This will be better organization and if we need to make it easier to configurize this location.

@pagrubel pagrubel mentioned this issue Nov 28, 2023
4 tasks
@pagrubel
Copy link
Collaborator Author

Closing this because it is covered in issue #734

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

1 participant