Do not underestimate his capacity to fuck things up.

th0mcat

Mar 24, 2023 • 1 min read

‌

Today, I woke up to a couple 500 errors on my Nextcloud calendars on my phone. Huh, that's weird, but forgot about it and turned on Plex, worked totally fine. Eventually I tried to hit Nextcloud, which responded with the same Internal Server Error. Uh oh, did my GitLab container go fucking crazy with logs again? What's the quickest way to find which folder is the issue? Of course, the quickest way is to go to Stack Overflow and find someone who's already solved the issue.

https://askubuntu.com/questions/911865/no-more-disk-space-how-can-i-find-what-is-taking-up-the-space

du -cha --max-depth=1 /var | grep -E "M|G"

Sure enough, the GitLab container was the culprit.

506G /var/lib/docker/containers/9ce673bc7c699c5bb45abaa9d3122a5e69c7667a1

A dramatic recreation of the events of this morning.

I should figure out why the GitLab image is doing that, but I also don't need to be running an entire suite of apps when Gitea also exists, so I'm just deleting Gitlab from my entire docker-compose.yaml.