boxcutter / debian Goto Github PK

Hi,
I don't understand why the iso_url is set at two different places:
In the Makefile, and pass to the -var option:

DEBIAN78_AMD64 ?= http://cdimage.debian.org/cdimage/release/7.8.0/amd64/iso-dvd/debian-7.8.0-amd64-DVD-1.iso
DEBIAN78_I386 ?= http://cdimage.debian.org/cdimage/release/7.8.0/i386/iso-dvd/debian-7.8.0-i386-DVD-1.iso
DEBIAN77_AMD64 ?= http://cdimage.debian.org/cdimage/archive/7.7.0/amd64/iso-dvd/debian-7.7.0-amd64-DVD-1.iso
DEBIAN77_I386 ?= http://cdimage.debian.org/cdimage/archive/7.7.0/i386/iso-dvd/debian-7.7.0-i386-DVD-1.iso
DEBIAN76_AMD64 ?= http://cdimage.debian.org/cdimage/archive/7.6.0/amd64/iso-dvd/debian-7.6.0-amd64-DVD-1.iso
DEBIAN76_I386 ?= http://cdimage.debian.org/cdimage/archive/7.6.0/i386/iso-dvd/debian-7.6.0-i386-DVD-1.iso
DEBIAN75_AMD64 ?= http://cdimage.debian.org/cdimage/archive/7.5.0/amd64/iso-dvd/debian-7.5.0-amd64-DVD-1.iso
DEBIAN75_I386 ?= http://cdimage.debian.org/cdimage/archive/7.5.0/i386/iso-dvd/debian-7.5.0-i386-DVD-1.iso
DEBIAN6010_AMD64 ?= http://cdimage.debian.org/cdimage/archive/6.0.10/amd64/iso-cd/debian-6.0.10-amd64-CD-1.iso
DEBIAN6010_I386 ?= http://cdimage.debian.org/cdimage/archive/6.0.10/i386/iso-cd/debian-6.0.10-i386-CD-1.iso

[…]

$(VIRTUALBOX_BOX_DIR)/$(1)$(BOX_SUFFIX): $(1).json $(SOURCES)
    rm -rf $(VIRTUALBOX_OUTPUT)
    mkdir -p $(VIRTUALBOX_BOX_DIR)
    $(PACKER_CMD) build -only=$(VIRTUALBOX_BUILDER) $(PACKER_VARS) -var "iso_url=$(2)" $(1).json

And directly in the .json file (for example: https://github.com/boxcutter/debian/blob/master/debian78.json#L168).

Regards,
Guillaume

λ packer build -only=virtualbox-iso -var-file=debian711.json debian.json
virtualbox-iso output will be in this color.

==> virtualbox-iso: Downloading or copying Guest additions
    virtualbox-iso: Downloading or copying: file:///C:/Program%20Files/Oracle/VirtualBox/VBoxGuestAdditions.iso
==> virtualbox-iso: Downloading or copying ISO
    virtualbox-iso: Downloading or copying: file:///Volumes/Storage/software/debian/debian-7.11.0-amd64-DVD-1.iso
    virtualbox-iso: Error downloading: open Volumes/Storage/software/debian/debian-7.11.0-amd64-DVD-1.iso: The system cannot find the path specified.
    virtualbox-iso: Downloading or copying: http://cdimage.debian.org/cdimage/archive/7.11.0/amd64/iso-dvd/debian-7.11.0-amd64-DVD-1.iso
==> virtualbox-iso: Starting HTTP server on port 8009
==> virtualbox-iso: Creating virtual machine...
==> virtualbox-iso: Creating hard drive...
==> virtualbox-iso: Creating forwarded port mapping for communicator (SSH, WinRM, etc) (host port 2736)
==> virtualbox-iso: Executing custom VBoxManage commands...
    virtualbox-iso: Executing: modifyvm debian711 --memory 512
    virtualbox-iso: Executing: modifyvm debian711 --cpus 1
==> virtualbox-iso: Starting the virtual machine...
==> virtualbox-iso: Waiting 10s for boot...
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Waiting for SSH to become available...

Installation process stucks at "Select a language" dialog:

or sometimes at "Configure the package manager" dialog:

Note: this time I am not behind a proxy. Packer version 0.10.1

The default iso download url is broken.

I did find a working url here but it does not seem to be the debian project official repo

https://atlas.hashicorp.com/box-cutter/boxes/debian81 fails to verify its existence.
Running vagrant init box-cutter/debian81; vagrant up --provider vmware_desktop fails with a 403 error.

Firstly, thanks for providing this service and sorry if this isn't the right place to raise this but I couldn't find another contact point.

debian82 box seems to have gone? I'm guessing this is because there is now a debian85 box instead?

Is the removal of debian82 a deliberate policy to force people on to the latest version? Was there any cross over period when debian82 and debian85 were available during which people should have upgraded? Is there an email list or push notification service that would have told users this?

It's just that anyone now trying to use my vagrant scripts for the first time will get 404 errors. They only work for me locally because I have debian82 cached.

I would be interested in:

• a policy of leaving debian82 in place for existing users. However I understand you may be wary about supplying out of date software, and I don't want to demand more work.
• could there be an announce only email list (Google Groups for a free service) so users can be aware of changes as they happen?
• could there be a debian8 box that will always be the latest version of debian8? Then those that don't care about minor differences can just run this and not have to worry about renaming debian82 to debian85.

But, again, thanks for the service!

@annawake @rasa FYI, b16f880 has undone #8

Hello @annawake, could you explain the rationale behind removing cmtool.sh in f39c56c? Thanks.

Hello @annawake

Would be cool, if you would update the virtualbox guest additions to 5.0.

Regards @dominikzogg

Hey guys, I'm tryin to build the images with Packer on a Windows 7 64bit host which is behind a corporate proxy and the process always stucks at the same step where the package manager should be configured ( error message: Bad archive mirror):

I have set proxy environment variables in Windows for http_proxy, https_proxy and no_proxy, e.g.:

λ echo $http_proxy
http://user:password@proxyhost:8888

(proxy uses authentification)

But it seems that my proxy environment variables are not forwarded to the virtual machine(?)

The use of deborphan in minimize.sh means that a bunch of necessary packages for Salt are removed when doing a versioned install of Salt via the cm_version var.

I spent a while playing around with deborphan, but couldn't come up with any way to mark the relevant packages as manual or similar which would make deborphan ignore them.

This is because Salt is installed from python source using pip when doing a versioned install. Salt's dependencies are installed via apt, and thus are "orphans".

Thoughts? Yet another -var and ENV var to avoid using deborphan during the packer build? I think that might be preferable to assuming that only a salt versioned install might benefit from ditching deborphan.

While Debian 9 (strech) was merged #53, and "Updated Debian 8 configs to new 8.8.0 release" #52
the Readme still says: "Current images are 8.6 and 7.11".

Please update the Readme.

Both the Debian 7 and 8 install processes ask for input (select grub boot device) and final confirmation before reboot. Of course, this breaks fully automated box generation. Maybe an issue with preseeding?

Hey, first thanks for maintaining these repos, they proved useful quite a few times to me already!

I noticed Debian's 7.7 version has gone missing from your Atlas account (and from this repo after a quick check), any chance you could bring it back? I've got some Debian 7.7 servers running atm and not planning to upgrade'em to 7.9 just yet... Of course I could just host a Debian 7.7 box by myself for my special needs but I thought it'd just feel great to have everything centralised in boxcutter repos?

Lemme know what you think :)
Thanks

Hi,

Could you please verify and correct the availability of the boxes ?

https://app.vagrantup.com/boxcutter/boxes/debian8

And all other boxes result in a 404 not found... so bad

Thank you very much !!!

The Parallels image available for Vagrant (v2.0.4) expands to 20GB, rathe than the usual 2-3GB for a base box.

Nothing seems to be using the space in the virtual environment.

Howdy,

Nice templates!
Any chance of you updating the Debian ones for Jessie which is currently at RC1?

Debian has again moved their old ISOs out of the way.

When building debian 9 for vmware this loops constantly

    vmware-iso: What is the location of the "ifconfig" program on your
    vmware-iso: machine?
    vmware-iso: The answer "" is invalid.  It must be the complete name of a binary file.

Since debian9 doesn't have ifconfig anymore a fix would be to add net-tools to the prelude-jessie.cfg. Would you like a PR for it?

https://github.com/dominikzogg/vagrant-php/issues/15

Would it possible to provide a vmware box for Wheezy 7.8?

Debian 8.8 and Debian 9 boxes are still missing at https://app.vagrantup.com/boxes/search?utf8=%E2%9C%93&sort=downloads&provider=&q=boxcutter+debian

Please update. Thanks.