Ejabberd fails to start when docker container id changes

rroemhild / docker-ejabberd

Dockerfile for Ejabberd server

MIT License

268 stars 160 forks source link

Ejabberd fails to start when docker container id changes #169

Open diegofal opened 6 years ago

diegofal commented 6 years ago

Currently, when ejabberd inits I can see this message:

"Application ejabberd started on node 'Mnesia@fe29feed088d'" -> after the @, "fe29feed088d" is the current container id.

When the container id changes, the database fails to start since the owner is attached to the previous container id.

Any thoughts on this? Thanks!!

rroemhild commented 6 years ago

This is how mnesia setup database. You can set ERLANG_NODE env to i.e. ejabberd@localhost and the mnesia database will be the same on each reboot / re-creation.