Recently i’ve ran into a problem, I am running 2 discourse forums, and I want to edit one, because its in an infinite redirect loop that I can only fix via discourse config, but can’t because I can’t stop the container. I don’t want to force it using kill or something, as that would possibly cause issues.
df -h and it returns
Filesystem Size Used Avail Use% Mounted on udev 16G 4.0K 16G 1% /dev tmpfs 3.2G 792K 3.2G 1% /run /dev/md2 20G 15G 4.0G 79% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 16G 2.2M 16G 1% /run/shm none 100M 0 100M 0% /run/user /dev/md3 1.8T 39G 1.7T 3% /home none 20G 15G 4.0G 79% /var/lib/docker/aufs/mnt/c4a287fb570f9d346f768e40d819f78466922b241ab53c3b4d0e67d1093e948f none 20G 15G 4.0G 79% /var/lib/docker/aufs/mnt/36c27719e26653039d1bac8fb1fc0337c45cd145eaad0b223cd5b5469b2ea295 shm 64M 4.0K 64M 1% /var/lib/docker/containers/5c7e37e4f1bb9339a900e19c6c74e918d0f0b0c76b4b3f23ed1cc342e1dbc610/shm shm 64M 4.0K 64M 1% /var/lib/docker/containers/3e83e4a36695fd4272863b5b9f3e8a08c3377fbc246b813173202c472112867a/shm
I ran the command
./launcher cleanup however, it does not free up any space. Any command using start/stop will not work, it just says it doesn’t have enough so it can’t continue.
The server has 2x2TB harddrives in raid 1, so space isn’t a problem in general.