Aug 25, 2009. I am doing another debian installation, same computer on another HD that previously had Vector linux. Debian Lenny stalled or failed at.or during select and install software. I tried goind down the line to see If I could install other options, those failed too. I then tried to install win xp. Geforce4 Mx 4000 Driver Windows 98. that stalled on format as.

I don't see any cause for this issue with the packer template and preseed you've got in that Github repo currently. I'm able to build that template and get a working linux install.

Where you should be looking is the preseed pkgsel lines, since you're not in an interactive install mode when you ask the installer to install a package that doesn't exist (in the configured repos) it errors in the way you're seeing. The preseed feature is super powerful, you can basically do anything to an install. It can be quite opaque to debug but with Packer we're also dropping into a provisioner once the install is done. In this case it's shell scripts, I'd recommend keeping preseed super basic and doing customisation down the line in your provisioner, make a new shell script to add new packages, do the other customisation you want baked into the image - even remove things that were installed by the preseed.

Once you're at the provisioning stage you can use the -debug switch in Packer to really get into debugging in a more tangible way - since the provisioners are shell scripts being run over an ssh connection on the working installed VM if you run into an issue you can also connect to that ssh or via the Virtualbox GUI and debug the running machine before it's cleaned up. The Bento project has excellent Packer templates you might like to use as reference - and - they created and maintained by Chef but Chef's not actually installed they're basically a vanilla Vagrant box. Basically - currently one of your package names in the preseed is bogus. I hope this helps! Edit: I thought it could be helpful to define some terms: HashiCorp software that automates the building of images. Basic workflow is Builder ->Provisioner ->Post Process • Builder: for the different virtualisation platforms e.g.

Virtualbox, Vmware, AWS EC2, Digital Ocean etc. Each has a different image format so we need to make an image for each. Builders typically make use of the operating system that's being installed unattended automation tools to provide a consistent base to be provisioned e.g. Debian/Ubuntu preseed, RHEL/Centos Kickstart etc. • Provisioner: Shell, Ansible, Chef, Salt, Puppet etc.

These run on all the installed basic images and are designed for configuration, installing software etc. • Post-Processors: Vagrant, Atlas, Amazon etc. Get your image ready for it's deployment targets. (There are a couple more optional workflow steps in Packer but those are the basics.).