I am trying to migrate an existing Discourse installation to Docker. This instance was installed and updated for a few months using the deprecated Ubuntu install instructions. I don’t have much space left on
/var. Only 687 MB.
When the bootstrap completes, here is the last part of the output:
 26 Mar 21:27:08.207 # Redis is now ready to exit, bye bye... 2014/03/26 14:27:22 Error: mkdir /var/lib/docker/aufs/diff/b0156136ca347a30a3c536a540d1074bba110e0e4a6b05620ef4528e28f71a3f/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.0.3/lib/rails/rack: no space left on device FAILED TO COMMIT 495c71a82e9a9b8e8b9e59d707ec62adae1581387fda77c75da4efcee81c7a20 Successfully bootstrapped, to startup use ./launcher start app
Here is my
df -h output on
Filesystem Size Used Avail Use% Mounted on /dev/mapper/lampsrv-var 6.0G 5.0G 687M 89% /var
The module that fails to get created or whatever varies each time. Am I correct in assuming that if I can get more space allocated to
/var that this will solve my problem and I can run Discourse again? What are the bounds on the space requirements of the bootstrap process? I’ve noticed that the space it uses grows and shrinks throughout the duration.