Testing Pandora FMS

[Unknown Member]

Hello,
I’m trying to test Pandora for new monitoring solution, and it’s great there’s a docker image available to setup a quick environment.
However, it seems that whenever i restart/recreate the container, and previous configuration is lost. Is there any way to make the data persistent through server reboots etc?
I’m using the described procedure:

docker run --name pandorafms pandorafms/pandorafms:7

Although, reformatted for docker-compose instead.

Good morning maw,

Its unusual that the previous configuration restarts when you restart the container, it could be a problem of the version you have. If you can try to do it with the version of today and test it it would be great. If the problem persists, can you send me the .conf of the server to see if something went wrong during the installation.

Alberto

[maw]

Like it

Up

0

Down

Drop it

::

Hello,
I’m trying to test Pandora for new monitoring solution, and it’s great there’s a docker image available to setup a quick environment.
However, it seems that whenever i restart/recreate the container, and previous configuration is lost. Is there any way to make the data persistent through server reboots etc?
I’m using the described procedure:

docker run --name pandorafms pandorafms/pandorafms:7

Although, reformatted for docker-compose instead.

Good morning maw,

Its unusual that the previous configuration restarts when you restart the container, it could be a problem of the version you have. If you can try to do it with the version of today and test it it would be great. If the problem persists, can you send me the .conf of the server to see if something went wrong during the installation.

Alberto

I just re-tested.
The configuration is intact when I restart the container. The dataloss occurs when I recreate the container, if I add another published port, add hostname etc.

I’m fairly new to the docker environment, so I’m not sure if this is the expected behaviour. But I have other docker containers running other miscellaneous stuff that retains their data just fine on recreation.
I attached the server conf in this post.

pandoraserver.txt

[Unknown Member]

Hello,
I’m trying to test Pandora for new monitoring solution, and it’s great there’s a docker image available to setup a quick environment.
However, it seems that whenever i restart/recreate the container, and previous configuration is lost. Is there any way to make the data persistent through server reboots etc?
I’m using the described procedure:

docker run --name pandorafms pandorafms/pandorafms:7

Although, reformatted for docker-compose instead.

Good morning maw,

Its unusual that the previous configuration restarts when you restart the container, it could be a problem of the version you have. If you can try to do it with the version of today and test it it would be great. If the problem persists, can you send me the .conf of the server to see if something went wrong during the installation.

Alberto

I just re-tested.
The configuration is intact when I restart the container. The dataloss occurs when I recreate the container, if I add another published port, add hostname etc.

I’m fairly new to the docker environment, so I’m not sure if this is the expected behaviour. But I have other docker containers running other miscellaneous stuff that retains their data just fine on recreation.
I attached the server conf in this post.

Good morning maw,

The normal way of function of docker with pandora is that if you recreate the container, the container will be destroyed and created again, so its normal that all the data is lost.

If you want to work with it you must:
1- Or only use stop, start and restart to use the pandora image in docker.
2- Or make an external installation of pandora, put it then on the docker container, and then you can recreate or do whatever you want because pandora will be stored externally.

Hope this helps you,

Alberto

[aeleus]

Like it

Up

0

Down

Drop it

::

Are there any plans to build a “true” Docker-capable version of Pandora? One where the configuration and data are separate from the application(s).

The current Docker-compose build is easy to deploy. Depending on bandwidth, it takes less than a minute to stand up a brand new installation. That’s great. The way the images are built though, that’s where the benefits of using Docker end.

If you make a change that requires recreating the container, you are back to zero.

If you update to the latest docker image, back to zero.

Want to roll back to the previous image version, back to zero.

Want to move Pandora to a different host, possible, but not as easy as it should be.

Docker is so much more than just a quick deployment tool.