Cleaning up tmp/sockets before starting application

[b-a-t]

After commiting altered version of the container one of the side effects of such an operation is that socket files are stored as plan files in the diff. One of such files is tmp/unicorn.socket, which prevents unicorn from starting up, as server sees it's not a socket and fails.

The easiest fix to that is to add a clean up into the appStart() function:

--- a/assets/init
+++ b/assets/init
@@ -443,6 +447,10 @@ esac
 chown -R redmine:redmine ${DATA_DIR}/tmp/

 appStart () {
+  # clear pids and sockets
+  rm -f /home/redmine/redmine/tmp/sockets/* /home/redmine/redmine/tmp/pids/*
+  #sudo -u redmine -H bundle exec rake tmp:pids:clear RAILS_ENV=production >/dev/null
+  #sudo -u redmine -H bundle exec rake tmp:sockets:clear RAILS_ENV=production >/dev/null
   # start supervisord
   exec /usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf
 }

[elderone]

+1

[sameersbn]

@b-a-t @elderone will do. I expected the two rake tasks to have the required effect. Apparently that does not seem to be the case.