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

Is the persistent volume required? #23

Open
alecisec opened this issue Oct 31, 2017 · 1 comment
Open

Is the persistent volume required? #23

alecisec opened this issue Oct 31, 2017 · 1 comment

Comments

@alecisec
Copy link

alecisec commented Oct 31, 2017

Not really an issue, more of a query on the build - what the impact of not having the volume (defined as follows)

volumes:
  - /data/misp:/var/www/MISP

remain persistent is. i.e. if the volume is not created, the container restarted and changes lost, the application appears to still run normally.

@ghost
Copy link

ghost commented May 30, 2018

Commenting out the volume mount instructions allowed my stack to start correctly.. It was a PITA and not starting for a long while.
"mysql:5.7" is the image in use and working.

"mysql/mysql-server:5.7" image did not work with or without commenting the volume mount instructions. (also tried ":Z" appended to the mount path with no joy.

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

1 participant