Skip to content
This repository has been archived by the owner. It is now read-only.

Windows 32-bit installer #14

Closed
TNick opened this issue Jun 17, 2014 · 21 comments

Comments

Projects
None yet
@TNick
Copy link

commented Jun 17, 2014

So, I'm the only one left with a Windows 7 32-bit, huh?
:)

@SvenDowideit

This comment has been minimized.

Copy link
Contributor

commented Jun 17, 2014

@TNick - I can't release what we can't test, so if you build and test that it works, we could do something.

@TNick

This comment has been minimized.

Copy link
Author

commented Jun 18, 2014

Changes listed below did the trick. I can fork and add a Boot2Docker-x86.iss if that is of any value. I was unable to run because error: VT-x is not available. (VERR_VMX_NO_VMX). I guess boot2docker.iso is a 64-bit image and this machine does not have VT-x. Yes, I could try to create a 32-bit image. :) But that's a game for another day.

diff --git a/Boot2Docker.iss b/Boot2Docker.iss
index 9e94996..75aa2df 100755
--- a/Boot2Docker.iss
+++ b/Boot2Docker.iss
@@ -14,7 +14,7 @@ SetupIconFile=boot2docker.ico
 ;DisableProgramGroupPage=yes
 ;DisableReadyPage=yes

-AppId={{05BD04E9-4AB5-46AC-891E-60EA8FD57D56}
+AppId={{DE3AFCFC-9BA5-4D7D-9CD0-292C00306990}
 AppCopyright=Docker Project
 AppContact=Sven Dowideit <SvenDowideit@docker.com>
 AppComments=http://docker.com/
@@ -25,15 +25,14 @@ AppPublisher={#MyAppPublisher}
 AppPublisherURL={#MyAppURL}
 AppSupportURL={#MyAppURL}
 AppUpdatesURL={#MyAppURL}
-ArchitecturesAllowed=x64
-ArchitecturesInstallIn64BitMode=x64
+ArchitecturesAllowed=x86
 DefaultDirName={pf}\{#MyAppName}
 DefaultGroupName=Docker
 ; lets not be annoying
 ;InfoBeforeFile=.\LICENSE
 ;DisableFinishedPage
 ;InfoAfterFile=
-OutputBaseFilename=docker-install
+OutputBaseFilename=docker-install-x86
 Compression=lzma
 SolidCompression=yes
 WizardImageFile=logo-docker-side.bmp
@@ -41,7 +40,7 @@ WizardSmallImageFile=logo-docker-small.bmp
 WizardImageStretch=no     
 WizardImageBackColor=$325461

-SignTool=ksign /d $qBoot2Docker for Windows$q /du $qhttp://docker.com$q $f
+;SignTool=ksign /d $qBoot2Docker for Windows$q /du $qhttp://docker.com$q $f

 [Languages]
 Name: "english"; MessagesFile: "compiler:Default.isl"
@@ -70,7 +69,7 @@ Source: ".\msys-Git\Git-1.9.0-preview20140217.exe"; DestDir: "{app}"; AfterInsta

 ;VirtualBox - 64 bit only
 ;https://forums.virtualbox.org/viewtopic.php?f=3&t=21127
-Source: ".\VirtualBox\VirtualBox-4.3.12-r93733-MultiArch_amd64.msi"; DestDir: "{app}"; Components: "VirtualBox"
+Source: ".\VirtualBox\VirtualBox-4.3.12-r93733-MultiArch_x86.msi"; DestDir: "{app}"; Components: "VirtualBox"
 Source: ".\VirtualBox\common.cab"; DestDir: "{app}"; AfterInstall: RunInstallVirtualBox(); Components: "VirtualBox"
 ; the cert http://www.catonrug.net/2013/03/virtualbox-silent-install-store-oracle-certificate.html
 ;Source: ".\VirtualBox\oracle-vbox.cer"; DestDir: "{app}"; AfterInstall: MSYSInstalled();  Components: "VirtualBox"

@SvenDowideit

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2014

mmm, ok, so you'll need a 32 bit kernel in a 32 bit iso, with a ...

and then with a vm set to use 2GB ram, we'll kill your box with swapping.

is it really worthwhile?

@TNick

This comment has been minimized.

Copy link
Author

commented Jun 19, 2014

nah, doesn't worth the effort. Thanks.

@jangondol

This comment has been minimized.

Copy link

commented Aug 16, 2014

@SvenDowideit - There is a related side-effect. It seems that you cannot run 64bit virtual machines inside virtual machines: https://web.archive.org/web/20140816155425/https://superuser.com/questions/713752/virtualbox-why-cant-i-create-a-64-bit-virtual-machine-inside-another-virtual

In other words, if you try to run Boot2Docker on a virtualized Win7-64 guest (this technically means running Virtualbox inside Virtualbox: Wow. Such meta. Very virtualization.), the boot process will halt with: This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU.

Coreinfo from Sysinternals says that VMX (Intel hardware-assisted virtualization) isn't enabled on the virtualized CPU (in the guest), even though it's available on the host. Win7-64 guest is started with VT-x (and Nested Paging) enabled. Both host and guest CPUs are reported as 64-bit. Virtualbox on the Win7-64 guest only allows creation of 32-bit virtual machines and the Acceleration tab in System settings is disabled.

So as long as Boot2Docker is 64-bit only (VT-x is required), you may not be able to run it inside a Virtualbox machine. Which could be useful (e.g. for development / testing purposes).

@SvenDowideit

This comment has been minimized.

Copy link
Contributor

commented Aug 16, 2014

Yeah, thats why I used vmware for testing boot2docker - it lets me run a virtualised OSX / Windows in which I can then run boot2docker. Given that the Docker daemon is amd64 only for now, I'm not sure what we gain from an i386 at this point (unless you're using it to work on multi-platform Docker support)

@jangondol

This comment has been minimized.

Copy link

commented Aug 19, 2014

@SvenDowideit - Hmmm... Tried running boot2docker on 64bit Windows under VMware and saw the same error message as in Virtualbox. I don't know the back-end details (tested on a VPS). Glad it worked for you though. :)

@SvenDowideit

This comment has been minimized.

Copy link
Contributor

commented Aug 20, 2014

yeah, VPS's don't necessarily allow nested VM's :/

@tianon

This comment has been minimized.

Copy link
Contributor

commented Oct 8, 2014

Heh this whole thread is gold; also, Docker upstream only supports 64bit, and I don't see that changing in the near future, but eventually maybe.

@ahmetb

This comment has been minimized.

Copy link
Contributor

commented Nov 12, 2014

This just happened to me on a 64-bit Windows 8. Solution was to uninstall Hyper-V from "Turn Windows features on and off" from Control Panel.

@trestletech

This comment has been minimized.

Copy link

commented Nov 12, 2014

@SvenDowideit , can you explain a bit more about your VMWare setup? I'm trying to run Boot2Docker on VMWare Fusion on my MacBook Pro but not having any luck regardless of how I fiddle the VMWare Windows machine or the boot2docker VirtualBox machine.

@trestletech

This comment has been minimized.

Copy link

commented Nov 12, 2014

Oops, I got it. For future Googlers...

In VMWare Fusion you can go to the settings of your VM, then:

"Processors & Memory" > "Advanced Options" > Check "Enable hypervisor applications in this VM". That got Boot2Docker working for me on a MacBook Pro, running Windows Server 2012 R2 in VMWare Fusion 6, running Boot2Docker v1.3.1

@SvenDowideit

This comment has been minimized.

Copy link
Contributor

commented Nov 12, 2014

bingo :)

@jangondol

This comment has been minimized.

Copy link

commented Nov 13, 2014

@trestletech - Cool workaround! Anyone aware of a similar trick for VirtualBox? (Tried googling to no avail...)

@ldsenow

This comment has been minimized.

Copy link

commented Nov 14, 2014

@ahmetalpbalkan, yes, it is Hyper-V.

@rtoip

This comment has been minimized.

Copy link

commented Dec 17, 2014

Hi, it seems I got it working: boot2docker/boot2docker#436

@memark

This comment has been minimized.

Copy link

commented Apr 27, 2015

@ahmetalpbalkan, instead of uninstalling Hyper-V, you can just disable it temporarily. Here's a way that works for me:
http://www.hanselman.com/blog/SwitchEasilyBetweenVirtualBoxAndHyperVWithABCDEditBootEntryInWindows81.aspx

@ahmetb

This comment has been minimized.

Copy link
Contributor

commented Apr 27, 2015

@memark ah nice to know thanks

@samayo

This comment has been minimized.

Copy link

commented Nov 23, 2015

@SvenDowideit It has been more than a year since this issue opened. Do you have any news? I'm also stuck with windows 7 32 bit. I had installed windows 10 but docker does not run on that also.

@StefanScherer

This comment has been minimized.

Copy link

commented Jan 22, 2016

A 32bit boot2docker.iso would help build some integration tests eg. for docker-machine to run on Travis, Circle, AppVeyor. They all do not support nested hypervisor, but should be able to spin up 32bit VM's.

@tianon

This comment has been minimized.

Copy link
Contributor

commented Feb 26, 2018

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).

@tianon tianon closed this Feb 26, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.