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

VOLUME /grassdb vs /actinia_core/grassdb? #135

Closed
neteler opened this issue Jan 5, 2021 · 1 comment
Closed

VOLUME /grassdb vs /actinia_core/grassdb? #135

neteler opened this issue Jan 5, 2021 · 1 comment
Assignees

Comments

@neteler
Copy link
Member

neteler commented Jan 5, 2021

There is an empty /grassdb/ in the deployed docker container while data really reside in /actinia_core/grassdb/.

Perhaps a wrong path here?

https://github.com/mundialis/actinia_core/blob/fdc0d91d83a528a0584cf206f701a057ba01bb6d/docker/actinia-core-alpine/Dockerfile#L142

Maybe the purpose is something else - then just disregard this issue.

@mmacata
Copy link
Member

mmacata commented Apr 8, 2021

We don't use it in our deployment but it might be useful for other users to have a persistent volume inside the docker container. As it doesn't disturb or add size to the image, we keep it.

@mmacata mmacata closed this as completed Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants