How to resize root partition on base image?

[Gonzo Fernandez]

Hi all,

I'm having issues getting packer/vagrant to have a bigger '/' (root) partition size. As of now I've only gotten it to 5.6 Gigs. I've built a packer base image and have set the base-virtualbox.json value 'disk_size' to 40000 (40 Gigs). I'm able to build the base image successfully and I have another .json packer file that builds the rest of my 'goodies' on top of that base image. The problem is that when I 'vagrant up' and it finishes building I login and only see root partition of 5.6 Gigs. Where are the 40 Gigs? I've looked online and people seem to say there is an issue with packer/vagrant resizing but I'm at a loss. Can anyone of you guys please help me before I blow my brains out....it's been a long day wrestling with this thing.

Thanks!

[Alvaro Miranda Aguilera]

can you put the template, scripts and response file on github for review?

the json set the size of the disk on the vm, but after that is the os that create the partitions, so maybe the issue is there

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/21a26a29-7f09-4f31-9561-777eb979af11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gonzo Fernandez]

Thank you Alvaro, yes the issue is with the OS creating the partition. I'm hoping there is a setting I can use to have the Os partition a bigger root directory. Would it be best to use a script to resize the partition somehow? Any existing examples would save me a lot of time. Thank you again for the response.

Gonzalo

You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/eeDUhiKEDto/unsubscribe.
To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ez4h7fFbr9mgrhdQyK9eLeXQJ0g7r5aL9Moa8Vs1dYQVA%40mail.gmail.com.

[Alvaro Miranda Aguilera]

hello

I may be missing something, but I think you haven't shared anything that can help you.

What commands you run, whats the output, what you see, what the host os, whats the guest, its Virtualbox? vmware? aws?

To unsubscribe from this group and all its topics, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ez4h7fFbr9mgrhdQyK9eLeXQJ0g7r5aL9Moa8Vs1dYQVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/90ED9CE1-7E1C-4D72-A1DE-A617A497A6FC%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gonzo Fernandez]

Hi Alvaro,

 Attached is my base image JSON. If you look you can specifically see that the image is set to 40Gigs. I use this base image to build a .box image that I use to Ansible provision all of my tools. Everything works well except the OS seems to not partition the right amount of space for root (/) directory. How can I have Packer or Vagrant assign more memory.

I found your response here but I was wondering if there was any update? : https://github.com/mitchellh/vagrant/issues/2339

ubuntu@opal-vagrant:~$ df -h

Filesystem                                   Size  Used Avail Use% Mounted on

udev                                            2.0G  4.0K  2.0G   1% /dev

tmpfs                                           396M  432K  395M   1% /run

/dev/dm-0                                    5.6G  4.5G  823M  85% /

none                                            4.0K     0  4.0K   0% /sys/fs/cgroup

none                                            5.0M     0  5.0M   0% /run/lock

none                                            2.0G  4.0K  2.0G   1% /run/shm

none                                            100M     0  100M   0% /run/user

/dev/sda1                                    236M   36M  188M  17% /boot

172.28.128.1:/Users/NFS/Shared 233G   77G  156G  34% /opt/opallabs

vagrant                                      233G   77G  156G  34% /vagrant

```

{

  "builders": [

  {

    "type": "virtualbox-iso",

    "vm_name": "base-ubuntu-1404",

    "guest_os_type": "Ubuntu_64",

    "format": "ova",

    "iso_url": "http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso",

    "iso_checksum": "bc09966b54f91f62c3c41fc14b76f2baa4cce48595ce22e8c9f24ab21ac8d965",

    "iso_checksum_type": "sha256",

    "ssh_username": "ubuntu",

    "ssh_password": "meowthis!!!",

    "ssh_wait_timeout": "20m",

    "headless": false,

    "vboxmanage": [

      ["modifyvm", "{{.Name}}", "--memory", "2048"],

      ["modifyvm", "{{.Name}}", "--cpus", "4"]

    ],

    "disk_size": "40000",

    "http_directory": "http",

    "boot_wait": "3s",

    "boot_command": [

      "<esc><wait>",

      "/linux noapic ",

      "preseed/url=http://{{ .HTTPIP }}:{{ .HTTPPort }}/allinone_preseed.cfg ",

      "hostname=ubuntu ",

      "debian-installer=en_US auto locale=en_US kbd-chooser/method=us ",

      "fb=false ",

      "keyboard-configuration/modelcode=SKIP keyboard-configuration/layout=USA ",

      "keyboard-configuration/variant=USA console-setup/ask_detect=false ",

      "initrd=/initrd.gz -- <enter>"

    ],

    "shutdown_command": "echo 'packer' | sudo -S shutdown -P now"

  }

  ],

  "provisioners": [

    {

      "type": "file",

      "source":  "files/base_vagrant_insecure_key.pub",

      "destination": "/tmp/base_vagrant_insecure_key.pub"

    },

    {

      "type": "shell",

      "scripts": [ "scripts/base_provision.sh"]

    }

  ]

}

```

On Thursday, October 6, 2016 at 9:57:43 AM UTC-7, Alvaro Miranda Aguilera wrote:

hello

I may be missing something, but I think you haven't shared anything that can help you.

What commands you run, whats the output, what you see, what the host os, whats the guest, its Virtualbox? vmware? aws?

On Thu, Oct 6, 2016 at 3:14 PM, Gonzo Fernandez <xxthe...@gmail.com> wrote:

Thank you Alvaro, yes the issue is with the OS creating the partition. I'm hoping there is a setting I can use to have the Os partition a bigger root directory. Would it be best to use a script to resize the partition somehow? Any existing examples would save me a lot of time. Thank you again for the response.

Gonzalo

On Oct 5, 2016, at 10:28 PM, Alvaro Miranda Aguilera <kik...@gmail.com> wrote:

can you put the template, scripts and response file on github for review?

the json set the size of the disk on the vm, but after that is the os that create the partitions, so maybe the issue is there

Alvaro

On Thu, Oct 6, 2016 at 2:03 AM, Gonzo Fernandez <xxthe...@gmail.com> wrote:

Hi all,

I'm having issues getting packer/vagrant to have a bigger '/' (root) partition size. As of now I've only gotten it to 5.6 Gigs. I've built a packer base image and have set the base-virtualbox.json value 'disk_size' to 40000 (40 Gigs). I'm able to build the base image successfully and I have another .json packer file that builds the rest of my 'goodies' on top of that base image. The problem is that when I 'vagrant up' and it finishes building I login and only see root partition of 5.6 Gigs. Where are the 40 Gigs? I've looked online and people seem to say there is an issue with packer/vagrant resizing but I'm at a loss. Can anyone of you guys please help me before I blow my brains out....it's been a long day wrestling with this thing.

Thanks!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/21a26a29-7f09-4f31-9561-777eb979af11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/eeDUhiKEDto/unsubscribe.

To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ez4h7fFbr9mgrhdQyK9eLeXQJ0g7r5aL9Moa8Vs1dYQVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/90ED9CE1-7E1C-4D72-A1DE-A617A497A6FC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Rickard von Essen]

Attach your allinone_preseed.cfg

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/83682ac0-6f8e-4555-9646-7a713c179551%40googlegroups.com.

[Gonzo Fernandez]

Attached is my pressed.cfg:

```

# Some inspiration:

# * https://github.com/chrisroberts/vagrant-boxes/blob/master/definitions/precise-64/preseed.cfg

# * https://github.com/cal/vagrant-ubuntu-precise-64/blob/master/preseed.cfg

# English plx

d-i debian-installer/language string en

d-i debian-installer/locale string en_US.UTF-8

d-i localechooser/preferred-locale string en_US.UTF-8

d-i localechooser/supported-locales en_US.UTF-8

# Including keyboards

d-i console-setup/ask_detect boolean false

d-i keyboard-configuration/layout select USA

d-i keyboard-configuration/variant select USA

d-i keyboard-configuration/modelcode string pc105

# Just roll with it

d-i netcfg/get_hostname string this-host

d-i netcfg/get_domain string this-host

d-i time/zone string UTC

d-i clock-setup/utc-auto boolean true

d-i clock-setup/utc boolean true

# Choices: Dialog, Readline, Gnome, Kde, Editor, Noninteractive

d-i debconf debconf/frontend select Noninteractive

d-i pkgsel/install-language-support boolean false

tasksel tasksel/first multiselect standard, openssh-server

pkgsel pkgsel/include/install-recommends boolean false

# Needed for VBox guest additions

pkgsel pkgsel/include string make gcc

#For the update

d-i pkgsel/update-policy select none

# Whether to upgrade packages after debootstrap.

# Allowed values: none, safe-upgrade, full-upgrade

d-i pkgsel/upgrade select safe-upgrade

# Stuck between a rock and a HDD place

d-i partman-auto/method string lvm

d-i partman-lvm/confirm boolean true

d-i partman-lvm/device_remove_lvm boolean true

d-i partman-auto/choose_recipe select atomic

d-i partman/confirm_write_new_label boolean true

d-i partman/confirm_nooverwrite boolean true

d-i partman/choose_partition select finish

d-i partman/confirm boolean true

# Write the changes to disks and configure LVM?

d-i partman-lvm/confirm boolean true

d-i partman-lvm/confirm_nooverwrite boolean true

d-i partman-auto-lvm/guided_size string max

d-i mirror/country string manual

d-i mirror/http/hostname string archive.ubuntu.com

d-i mirror/http/directory string /ubuntu

# No proxy, plx

d-i mirror/http/proxy string

d-i apt-setup/services-select multiselect security

d-i apt-setup/security_host string security.ubuntu.com

d-i apt-setup/security_path string /ubuntu

# Default user, change

d-i passwd/root-login boolean false

d-i passwd/user-fullname string ubuntu

d-i passwd/username string ubuntu

d-i passwd/user-password password meowthis!!!

d-i passwd/user-password-again password meowthis!!!

# sudo without password

d-i passwd/user-default-groups sudo

d-i user-setup/encrypt-home boolean false

d-i user-setup/allow-password-weak boolean true

d-i preseed/late_command string echo "%sudo ALL=(ALL:ALL) NOPASSWD:ALL" >> /target/etc/sudoers;sync

# Go grub, go!

d-i grub-installer/only_debian boolean true

d-i finish-install/reboot_in_progress note

```

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt86bbfVFhEqq2_N%3DDC-Nr02Z%3DBWagSyYf2fNi5nAApMoQ%40mail.gmail.com.

[Gonzo Fernandez]

Hi Richard, 

I think you pointed me in the right direction here. It seems like my preseed file might be the ticket. If you look at `d-i partman-auto/choose_recipe select atomic`, this should put everything into the / directory, right? I'm not sure why it's not using the full allotted 40GB's I've stated in the Packer file though. Am I doing something wrong?

Attach your allinone_preseed.cfg

[Alvaro Miranda Aguilera]

On Mon, Oct 10, 2016 at 7:48 PM, Gonzo Fernandez <xxthe...@gmail.com> wrote:

d-i partman-lvm/device_remove_lvm boolean true

d-i partman-auto/choose_recipe select atomic

no sure whats different

but can you try once with this preseed?

https://github.com/cbednarski/packer-ubuntu/blob/master/http/preseed.cfg

Packer just create the VM disk, but from there is the OS that is doing the partition layout and sizes.

Alvaro.

--

Alvaro

[Gonzo Fernandez]

Hi Alvaro, I’ll give it a try with your preseed.cfg.

Something strange is happening here. I changed up the pre-seed file with this one (notice the red text):

# Use LVM for partitioning

d-i   partman-auto/method string lvm

d-i partman-auto-lvm/guided_size string max

# If one of the disks that are going to be automatically partitioned

# contains an old LVM configuration, the user will normally receive a

# warning. Preseed this away

d-i     partman-lvm/device_remove_lvm boolean true

# And the same goes for the confirmation to write the lvm partitions.

d-i     partman-lvm/confirm boolean true

# Really, please don't prompt me!

d-i     partman-lvm/confirm_nooverwrite boolean true

#  partitioning

# Physical partitions:

# 1. BIOS boot partition: 1 MB See https://wiki.archlinux.org/index.php/GRUB2#GUID_Partition_Table_.28GPT.29_specific_instructions

# 2. Boot partition: 250 MB

# 2. LVM, with the following logical volumes

#     - Root partition: 250 GB (256000 MB), ext4.

#     - Swap: 100% of RAM

#     - Data partition: remaining space, XFS

d-i partman-auto/expert_recipe string                         \

      boot-root ::                                            \

              1 1 1 free method{ biosgrub } .                 \

              250 250 250 ext2                                \

                      $primary{ } $bootable{ }                \

                      method{ format } format{ }              \

                      use_filesystem{ } filesystem{ ext2 }    \

                      mountpoint{ /boot }                     \

              .                                               \

              100% 2048 100% linux-swap                       \

                      lv_name{ swap }                         \

                      method{ swap } format{ }                \

                      $lvmok{ }                               \

              .                                               \

              20000 40000 40000 ext4                          \

                      lv_name{ root }                         \

                      method{ lvm } format{ }                 \

                      use_filesystem{ } filesystem{ ext4 }    \

                      mountpoint{ / }                         \

                      $lvmok{ }                               \

              .

# This makes partman automatically partition without confirmation, provided

# that you told it what to do using one of the methods above.

d-i     partman-partitioning/confirm_write_new_label boolean true

d-i     partman/choose_partition select finish

d-i     partman/confirm boolean true

d-i     partman/confirm_nooverwrite boolean true

d-i grub-installer/only_debian boolean true

d-i grub-installer/with_other_os boolean true

d-i mirror/country string manual

d-i mirror/http/hostname string archive.ubuntu.com

d-i mirror/http/directory string /ubuntu

# No proxy, plx

d-i mirror/http/proxy string

d-i apt-setup/services-select multiselect security

d-i apt-setup/security_host string security.ubuntu.com

d-i apt-setup/security_path string /ubuntu

# Default user, change

d-i passwd/root-login boolean false

d-i passwd/user-fullname string ubuntu

d-i passwd/username string ubuntu

d-i passwd/user-password password meowthis!!!

d-i passwd/user-password-again password meowthis!!!

# sudo without password

d-i passwd/user-default-groups sudo

d-i user-setup/encrypt-home boolean false

d-i user-setup/allow-password-weak boolean true

d-i preseed/late_command string echo "%sudo ALL=(ALL:ALL) NOPASSWD:ALL" >> /target/etc/sudoers;sync

# Go grub, go!

d-i grub-installer/only_debian boolean true

d-i finish-install/reboot_in_progress note

```

Once the base ova file was built, I `packer build my-allinone.json`, which contains:

```

{

  "variables": {

    "base-image": "output-virtualbox-iso/base-ubuntu-1404.ova"

  },

  "builders": [

  {

    "type": "virtualbox-ovf",

    "source_path": "{{user `base-image`}}",

    "ssh_username": "ubuntu",

    "ssh_password": "meowthis!!!",

    "ssh_wait_timeout": "30s",

    "shutdown_command": "echo 'packer' | sudo -S shutdown -P now",

    "vboxmanage": [

      ["modifyvm", "{{.Name}}", "--memory", "2048"],

      ["modifyvm", "{{.Name}}", "--cpus", "4"],

      ["modifyvm", "{{.Name}}", "--natdnshostresolver1", "on"],

      ["modifyvm", "{{.Name}}", "--natdnsproxy1", "on"]

    ],

    "headless": true,

    "guest_additions_mode": "disable"

  }

  ],

  "provisioners": [

    {

      "type": "shell",

      "script": "scripts/base-packages.sh"

    },

    {

      "type": "ansible-local",

      "inventory_file": "inventory/allinone",

      "command": "ansible-playbook",

      "playbook_file": "../playbooks/bootstrap.yml",

      "playbook_dir": "../playbooks",

      "role_paths": [

                "../roles/yaegashi.blockinfile",

                "../roles/ANXS.nodejs",

                "../roles/ANXS.build-essential",

                "../roles/vagrant",

                "../roles/mysql",

                "../roles/Stouts.source",

                "../roles/zenoamaro.postgresql",

                "../roles/postgresql",

                "../roles/DavidWittman.redis",

                "../roles/my.application",

                "../roles/ruby_install",

                "../roles/zzet.rbenv"

            ]

    },

    {

      "type": "shell",

      "scripts": [ "scripts/allinone_cleanup.sh"]

    }

  ],

  "post-processors": [

    {

      "type": "vagrant",

      "output": “my-allinone-{{.Provider}}.box"

    }

  ]

}

```

The scripts that I use in the `my-allinone.json` file do not contain anything other than some `apt-get install` and `apt-clean` commands. Once this creates the VirtualBox `.box` file I run `vagrant up` and my machine is built.

Here is the output with the new pressed.cfg listed above:

```

ubuntu@vagrant:~$ df -h

Filesystem                                   Size  Used Avail Use% Mounted on

dev                                             2.0G  4.0K  2.0G   1% /dev

tmpfs                                           396M  432K  395M   1% /run

/dev/dm-0                                    5.6G  4.5G  822M  85% /

none                                           4.0K     0  4.0K   0% /sys/fs/cgroup

none                                           5.0M     0  5.0M   0% /run/lock

none                                           2.0G  4.0K  2.0G   1% /run/shm

none                                          100M     0  100M   0% /run/user

/dev/sda1                                   236M   36M  188M  17% /boot

172.28.128.1:/Users/gonzofernandez/shared 233G   77G  157G  33% /opt/nfs_share

vagrant                                      233G   77G  157G  33% /vagrant

```

As you can see, it doesn’t seem to be listening to my preseed file as it partitions whatever it likes. Alvaro, I’ll try your preseed file and see if that works. I’ll update soon. Thanks for your help!

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/eeDUhiKEDto/unsubscribe.
To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ex1hG-bwjVDy0gEXM2x4WpBRyOGg6zHRvJofQ-0XPP_0g%40mail.gmail.com.

[Gonzo Fernandez]

Just an update, I've tried using your preseed.cfg file: https://github.com/cbednarski/packer-ubuntu/blob/master/http/preseed.cfg

Unfortunately this did not work as it still doesn't partition enough space to the root drive (/) :(

I'm going crazy with this as it's very frustrating. I'm not sure what else it could be.

ubuntu@opal-vagrant:~$ sudo fdisk -l

Disk /dev/sda: 21.0 GB, 20971520000 bytes

255 heads, 63 sectors/track, 2549 cylinders, total 40960000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x0004f51f

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *        2048      499711      248832   83  Linux

/dev/sda2          501758    16775167     8136705    5  Extended

/dev/sda5          501760    16775167     8136704   8e  Linux LVM

Disk /dev/mapper/ubuntu--vg-root: 6182 MB, 6182404096 bytes

255 heads, 63 sectors/track, 751 cylinders, total 12075008 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition table

Disk /dev/mapper/ubuntu--vg-swap_1: 2147 MB, 2147483648 bytes

255 heads, 63 sectors/track, 261 cylinders, total 4194304 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition table

ubuntu@opal-vagrant:~$ df -h

Filesystem                                   Size  Used Avail Use% Mounted on

udev                                            2.0G  4.0K  2.0G   1% /dev

tmpfs                                           396M  432K  395M   1% /run

/dev/dm-0                                    5.6G  4.5G  822M  85% /

none                                            4.0K     0  4.0K   0% /sys/fs/cgroup

none                                            5.0M     0  5.0M   0% /run/lock

none                                            2.0G  4.0K  2.0G   1% /run/shm

none                                           100M     0  100M   0% /run/user

/dev/sda1                                    236M   36M  188M  17% /boot

172.28.128.1:/Users/gonzofernandez/shared  233G   77G  157G  33% /opt/shared

vagrant                                        233G   77G  157G  33% /vagrant

[Alvaro Miranda Aguilera]

Hi Gonzalo,

If you can share your project in a github repo I can check for you.

Thanks

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/1c8cf854-08b0-409b-980c-000e0ec04360%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gonzo Fernandez]

Hi Alvaro,

Here is my repo: https://github.com/xxthegonzxx/packer-base

Feel free to try it out. I would love some feedback. Thanks!

You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/eeDUhiKEDto/unsubscribe.

To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ezRtYEx00Yqy9%2B3pLL-t_Pi7N0ebJFHB6nrFH-ETCCaMg%40mail.gmail.com.

[Alvaro Miranda Aguilera]

hello

i did build the base one.

template say 40gb, it does create a LVM with / of 38gb, being 2gb used in boot/swap

so, it did work for me.

packer 0.10.2

can we go back a  bit on what you expect to have that is not working?

Thanks

Alvaro.

To unsubscribe from this group and all its topics, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0ezRtYEx00Yqy9%2B3pLL-t_Pi7N0ebJFHB6nrFH-ETCCaMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/82D11C78-9A22-4546-BA8B-C2C4B82AB64A%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gonzo Fernandez]

So I did some more research and it looks like I can import the .ova file that gets created and you’re right, the OS does create root ( / ) of 38GB’s with the rest being used in boot/swap. 

I think I might have found what the issue was. It looks like my packer-cache was pointing to an old VMDK file that wasn’t updated. I deleted this file:

 

``` /Users/gonzofernandez/.vagrant.d/boxes/allinone-virtualbox/0/virtualbox/packer-virtualbox-ovf-1476217271-disk1.vmdk ```

then I rebuilt with `packer build allineone_virtualbox.json`. This built my new VM with all the goodies installed on it. Then I simply `vagrant up` and checked the disk:

ubuntu@vagrant:~$ df -h

Filesystem                   Size  Used Avail Use% Mounted on

/dev/mapper/ubuntu--vg-root   38G  5.3G   30G  15% /

none                         4.0K     0  4.0K   0% /sys/fs/cgroup

udev                         2.0G  4.0K  2.0G   1% /dev

tmpfs                        396M  392K  395M   1% /run

none                         5.0M     0  5.0M   0% /run/lock

none                         2.0G  4.0K  2.0G   1% /run/shm

none                         100M     0  100M   0% /run/user

/dev/sda1                    236M   36M  188M  16% /boot

Looks like that did it!

I want to thank you Alvaro for helping me troubleshoot this. You’ve made my day! Thanks bud!

To unsubscribe from this group and all its topics, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAHqq0eyMAhd4aG%2BT9gyT8wWfEd9RKG8LTSM_j926MerDmC9eow%40mail.gmail.com.