This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.

⚠️ We've moved!

Hi there!

To reduce project dependency on 3rd party paid services the StackStorm TSC has decided to move the Q/A from this forum to Github Discussions. This will make user experience better integrated with the native Github flow, as well as the questions closer to the community where they can provide answers.

Use 🔗 Github Discussions to ask your questions.

Reg st2-docker persistancy

Operations
#1

hi Team,

Please help to know, what are all the ways the st2-docker could be persisted in the case of docker restarted or the system reboot.
I should not be losing any changes, it should work as before or with minimal changes. Please guide.
other than the below any other volumes are to be created/added. As I was seeing st2chatops.env variable is reset to the initial when the system rebooted or docker is restarted.

volumes:
mongo-volume:
mongo-configdb-volume:
postgres-volume:
rabbitmq-volume:
redis-volume:
stackstorm-packs-volume:
stackstorm-virtualenvs-volume:
stackstorm-configs-volume:
stackstorm-log-volume:

#2

Hi,

I did not use st2-docker with chatops yet but I can’t remember that I ever lost anything. So you may be good to go by just adding a new volume like stackstorm-chatops-volume:/opt/stackstorm/chatops to persist the chatops configuration as well.

Cheers,
Marcel

#3

Thanks a lot, got it.

1 Like