Re: Vagrant disk size
Le 10/02/2018 à 11:13, Gero Müller a écrit : > Hi! > > Thanks for your reply. Unfortunately /vagrant does not fulfil the > requirements for building raspberry images, no special/dev files. Even > NFS does not work. > > Cheers > Gero OK I see. Can you submit a bug report on bts.debian.org againtst the cloud.debian.org package, describing your issue > I have to see if we can cover that with a bigger disk image, or if having an end user doc is enough to cover that. Maybe cloud-initramfs-growroot can help too here, but we need to avoid the whole cloud-init stuff ( 7s slowdown at boot ) if we can. apt-cache show cloud-initramfs-growroot | grep ^Description: Description: automatically resize the root partition on first boot IIRC for this too work the root partition has to be the last one in the partition table.
Re: Vagrant disk size
Hi! Thanks for your reply. Unfortunately /vagrant does not fulfil the requirements for building raspberry images, no special/dev files. Even NFS does not work. Cheers Gero Am 10.02.2018 um 20:08 schrieb Emmanuel Kasper: > Le 10/02/2018 à 04:09, Gero Müller a écrit : >> Hi! >> >> Could you increase the disk size of the debian/stretch64 and >> debian/contrib-stretch64 boxes? Added disk or resizing disks in not easy >> enough and ~7GB is not much to work with nowadays (building RaspberryPi >> images) 32GB should be good and not increase the download size by much. >> >> Thanks alot! >> Gero >> > > Hi Gero > Thanks for your interest on the Debian Vagrant Boxes. > You should do your build insided the /vagrant directory when using the > contrib-stretch64 box. > > This directory is exported from your host to the vagrant guest via > vboxfs, so when writing suff in /vagrant, you're not limited by the disk > image size of the vagrant guest. > ( try df --human /vagrant inside this box ) > > > debian/stretch64 boxes don't have this, so I recommend you to use > contrib-stretch64 if you need a lot of disk space. > > Emmmanuel >
Re: Vagrant disk size
Le 10/02/2018 à 04:09, Gero Müller a écrit : > Hi! > > Could you increase the disk size of the debian/stretch64 and > debian/contrib-stretch64 boxes? Added disk or resizing disks in not easy > enough and ~7GB is not much to work with nowadays (building RaspberryPi > images) 32GB should be good and not increase the download size by much. > > Thanks alot! > Gero > Hi Gero Thanks for your interest on the Debian Vagrant Boxes. You should do your build insided the /vagrant directory when using the contrib-stretch64 box. This directory is exported from your host to the vagrant guest via vboxfs, so when writing suff in /vagrant, you're not limited by the disk image size of the vagrant guest. ( try df --human /vagrant inside this box ) debian/stretch64 boxes don't have this, so I recommend you to use contrib-stretch64 if you need a lot of disk space. Emmmanuel -- You know an upstream is nice when they even accept m68k patches. - John Paul Adrian Glaubitz, Debian OpenJDK maintainer
Re: Vagrant disk size
On 10 February 2018 03:09:45 GMT, "Gero Müller" wrote: >Hi! > >Could you increase the disk size of the debian/stretch64 and >debian/contrib-stretch64 boxes? Added disk or resizing disks in not >easy >enough and ~7GB is not much to work with nowadays (building RaspberryPi >images) 32GB should be good and not increase the download size by much. I think that instead we should fix resizing but I'm not volunteering for this task.
