The open-nti container doesn't appear persistent between container stops and starts

[juniper]

The open-nti container doesn't appear persistent between container stops and starts

[3fr61n]

Hi

This is a inherit behaviour from docker philosophy, in you want to make your changes persistent after stoping the container, you need first to 'commit' your container state (please check last section of this link https://docs.docker.com/engine/quickstart/), then make sure to rename/tag your new images with the proper tag (you can override the original image tags), and then start your container from the latest image you just commited

Regards
Efrain

[mdbarrett99]

Hi,

Yep appreciate this and probably haven't asked the question properly. I was talking with Damian offline and he informs me grafana configuration files are inside the container (as to my example), but the database is outside the container. I said that would be a very useful addition to move them outside the container (so we can add users to be persistent etc) - whilst typing I noticed issue 8 was just raised.

In addition I guess where this problem really originated from was the influxd database doesn't appear to be persistent. Looking at the docker.start.sh file in theory /var/lib/influxdb inside the container is mapped to $(pwd)/db outside the container as a volume. If I ssh to the container, I do see the mapping, but once again nothing is being written to that directory so I'm not sure what is going on there.

Cheers.

M

[3fr61n]

It seems there is another thread about the same issue, #8 , so I'm closing this one