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

Fix "beeflow core pull-deps" to use a Dockerfile to pull the neo4j container and add the apoc file #943

Open
pagrubel opened this issue Oct 8, 2024 · 0 comments
Assignees
Labels
bug Something isn't working High Priority

Comments

@pagrubel
Copy link
Collaborator

pagrubel commented Oct 8, 2024

beeflow core pull-deps should use a Dockerfile to build the needed neo4j container and add the apoc file

This dockerfile should be placed in beeflow/data/dockerfiles and should be used by the ci integration tests so we only need to modify it in one place.

Also, if a user uses "beeflow core pull-deps" to have their own dependent containers, they should be used in the bee.conf file. Consider automatically editting it and removing the ~/.beeflow/deps directory. Beeflow should not be running when this is done, so adding a check for that should probably be done.

@pagrubel pagrubel mentioned this issue Oct 8, 2024
10 tasks
@pagrubel pagrubel added High Priority bug Something isn't working labels Oct 8, 2024
@Leahh02 Leahh02 self-assigned this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working High Priority
Projects
None yet
Development

No branches or pull requests

2 participants