The Vagrant configuration described in the provided Vagrantfile does not specify the disk size, thus leaving the choice to the virtualisation provider. In case of VirtualBox, the default disk size, when not specified, is 10 GB.
When trying to run docker-compose with the full infrastructure setup, it stops at the kibana steps because it runs out of disk space.
vagrant@ubuntu-bionic:~/src/my-site$ docker-compose -f docker-compose.full.yml up -d
Pulling kibana (docker.elastic.co/kibana/kibana-oss:7.2.0)...
7.2.0: Pulling from kibana/kibana-oss
48914619bcd3: Already exists
f2bc79fc77ab: Pull complete
1ebe2db78ce5: Extracting [==================================================>] 97.65MB/97.65MB
f1e2b4f43bdd: Download complete
b0ef6d560815: Download complete
7d6d6c5a5bfe: Download complete
2492572a3fe4: Download complete
5ee5d10f355d: Download complete
ERROR: failed to register layer: Error processing tar file(exit status 1): write /usr/share/kibana/src/legacy/ui/public/chrome/api/angular.js: no space left on device
Note that resizing the partition / Guest OS disk after the creation is not trivial
Steps to Reproduce
Follow the instructions for Vagrant until part 03 of the tutorial.
Describe the bug
The Vagrant configuration described in the provided Vagrantfile does not specify the disk size, thus leaving the choice to the virtualisation provider. In case of VirtualBox, the default disk size, when not specified, is 10 GB.
When trying to run
docker-composewith the full infrastructure setup, it stops at the kibana steps because it runs out of disk space.Note that resizing the partition / Guest OS disk after the creation is not trivial
Steps to Reproduce
Follow the instructions for Vagrant until part 03 of the tutorial.