Paul Slavickas

I just had a quick question regarding this docker instance of GitLab-CE: After first starting the docker for the first time I noticed that it started spamming the local docker logs and took up > 20GB of memory within the first hour using the default configuration. Everything is working great now after disabling the puma workers in the /etc/gitlab/gitlab.rb file as follows: puma['min_threads'] = 0 puma['max_threads'] = 0 Unfortuantely, I am still having a problem when this docker auto-updates as it stomps on the local /etc/gitlab/gitlab.rb changes.. which then effectively kills my unraid server within a few hours (128GB!!). I'm assuming some of you have experienced this? I was hoping that someone has figured out a way for future updates to avoid stomping on local /etc/gitlab/gitlab.rb changes. Thanks!!