Closed bradwbradw closed 1 year ago
Sorry for the late reply.
This is due to us not properly handling the start/stop status of a container in the pre-restore
trigger. That trigger is called on server reboot, via dokku ps:restore
.
The unfortunate thing is that unless a container is destroyed, docker will restart it on server boot (not sure why, thats just been my annoying experience) even if you manually stop it. As such, I think if you don't want a service running on reboot, the best way is to run the :stop
subcommand so the container won't exist (that pauses and removes the container).
Ah a small update: The :stop
command is what you want now. There is a new :pause
that simply stops the container, while :stop
also removes it.
Description of problem
My mongo service
abc
is connected to an appxyz
that is "exited". it was stopped manually and dokku does not start it up (correct behaviour).I wouldn't expect the connected mongo to start up if the host app isn't running, but it does start. I see status: running when using
dokku mongo:info abc
.Even if i run
dokku mongo:stop abc
that will stop the mongo instance, but it starts up automatically on server reboot, even though I stopped it manually (contrary to the behaviour of apps)How reproducible
reproducible
Steps to Reproduce
xyz
, mongo serviceabc
, connect them.xyz
dokku ps:stop xyz
dokku mongo:stop abc
Actual Results
dokku mongo:info abc
shows Status=running`Expected Results
dokku mongo:info abc
shows Status=exited`Environment Information
dokku report APP_NAME
outputThanks for any help, or workaround suggestions
How (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Digital Ocean, debian installation.
Additional information
n/a