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

Docker images lacks proper data management #418

Closed
arkenoi opened this issue Mar 13, 2017 · 4 comments
Closed

Docker images lacks proper data management #418

arkenoi opened this issue Mar 13, 2017 · 4 comments

Comments

@arkenoi
Copy link
Member

arkenoi commented Mar 13, 2017

It is basically a VM-like deployment -- importing configuration, exporting logs, performing data backups is complicated since data volumes are not used.

@MrSeccubus
Copy link
Member

Can you elaborate?
Configuration is settable via ENV variables as is the Docker way.
What is it you would have expected.

@arkenoi
Copy link
Member Author

arkenoi commented Mar 14, 2017

that's not much of configuration that we can pass via current environment settings. data volume is a good tool to separate private container data/code from public. i will play a little bit more with it.

@arkenoi
Copy link
Member Author

arkenoi commented Mar 15, 2017

crontabs, yes.
next things are SSL certificates (both for server and SSL validation)

btw I think disabling SSL certificate validation for local nessus installations by default is bad idea
maybe we need a way to auto fetch it the first time

@MrSeccubus
Copy link
Member

Crontab, ssl certs and mySQL database can now be stored on the data volume since PR #411

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