-
Notifications
You must be signed in to change notification settings - Fork 141
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
Persistent storage using the default settings doesn't survive 'docker compose down' #34
Comments
Does this mean the entire database is re-created every time? |
I'll have to double-check the database entries. Interestingly when I do a docker compose down && up I'm seeing the inputs preserved, but the node_id isn't preserved, so all my inputs that had a local node set are all disabled until I specifiy a new node. I seem to remember from playing with Postgres that even though it's dockerised it's still using the host filesystem for storage - perhaps mariadb does the same, making it immune to container deletion? |
The data is persisted by default (with the volume mount defined in the In the docker-compose.yml, the environment variable Simply add services:
graylog:
[...]
volumes:
# Persist the graylog config
- "graylog_cfg:/usr/share/graylog/data/config"
volumes:
[...]
# Define the volume
graylog_cfg: to ensure that the |
It looks to me that this is the same issue as this:
graylog_data should point to /usr/share/graylog/data. Also graylog_journal should point to an own path, eg. /usr/share/graylog/journal, and in graylog.conf
|
I was trying to track down why my stream ID's were changing.
The provided docker compose files attempt persistent storage by using volumes (top level), and mounting graylog files within.
The volumes however are not persistent and are remade after a docker compose down and up.
The text was updated successfully, but these errors were encountered: