Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container exits after a while #2

Open
NicolasLM opened this issue Oct 4, 2017 · 1 comment
Open

Container exits after a while #2

NicolasLM opened this issue Oct 4, 2017 · 1 comment

Comments

@NicolasLM
Copy link

First thank you for crafting this image. We've been using it for a while without problems until recently, when it started to stop itself quite quickly:

$ docker run -ti --rm -p 783:783 dinkel/spamassassin
Oct 04 14:33:27.520495 check[11]: [ 2] [bootup] Logging initiated LogDebugLevel=3 to file:/dev/stderr
Oct  4 14:33:29.303 [11] info: spamd: server started on IO::Socket::IP [0.0.0.0]:783 (running version 3.4.1)
Oct  4 14:33:29.303 [11] info: spamd: server pid: 11
Oct  4 14:33:29.306 [11] info: spamd: server successfully spawned child process, pid 14
Oct  4 14:33:29.309 [11] info: spamd: server successfully spawned child process, pid 15
Oct  4 14:33:29.310 [11] info: prefork: child states: IS
Oct  4 14:33:29.310 [11] info: prefork: child states: II
  
/run.sh: line 25:     7 Terminated              /rule-update.sh
/run.sh: line 25:     8 Terminated              /spamd.sh
@NicolasLM
Copy link
Author

NicolasLM commented Oct 4, 2017

Maybe the run.sh tries to do too much. The problem is solved by replacing it by:

#!/bin/bash
set -m

./rule-update.sh &
exec ./spamd.sh

Of course with this approach the container will still run even if the update fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant