kaosagnt / toolbox2docker Goto Github PK

Hello! This is not an issue, actually, but rather a question: how to change local IP address used by docker?

$ docker-machine ip
192.168.99.105

I would like to change it back to 192.168.99.101 which I used to - is it possible?
Thank you.

Hey Ian,

just wanted to thank you for the work you put into maintaining this docker toolbox fork.

I need to use virtualbox and docker at the same time on my windows workstation - which does not work with docker desktop as it requires hyper-v. enabling hyper-v however still renders virtualbox completely unusable.

Kind Regards,
Seb

I am trying to use toolbox2docker on Windows 10. As reported in #3 I also realized that an old boot2docker.iso file is downloaded by default.

However it does not seem to be possible on Windows to reference the boot2docker.iso file that comes with toolbox2docker. No matter what kind of file URL I try to feed into the --virtualbox-boot2docker-url parameter of docker-machine I either receive:

Error creating machine: Error in driver during machine creation: open .../boot2docker.iso: The filename, directory name, or volume label syntax is incorrect.

or

Error creating machine: Error in driver during machine creation: Panic in the driver: runtime error: invalid memory address or nil pointer dereference
goroutine 71 [running]:
runtime/debug.Stack(0x1a37bc0, 0x0, 0x22988c0)
        /usr/local/go/src/runtime/debug/stack.go:24 +0xa4
github.com/docker/machine/libmachine/drivers/rpc.(*StandardStack).Stack(0x36c2fc0, 0x1a37bc0, 0x368c050, 0x22988c0)
        /go/src/github.com/docker/machine/libmachine/drivers/rpc/server_driver.go:23 +0x29
github.com/docker/machine/libmachine/drivers/rpc.trapPanic(0xc00018fc00)
        /go/src/github.com/docker/machine/libmachine/drivers/rpc/server_driver.go:129 +0x9b
panic(0x1a37bc0, 0x368c050)
        /usr/local/go/src/runtime/panic.go:522 +0x1c3
github.com/docker/machine/libmachine/mcnutils.(*b2dReleaseGetter).download(0xc0001485b0, 0xc00042b280, 0x33, 0x1e3dd30, 0xf, 0xc0000b0080, 0x31, 0x0, 0x0)
        /go/src/github.com/docker/machine/libmachine/mcnutils/b2d.go:198 +0x67
github.com/docker/machine/libmachine/mcnutils.(*B2dUtils).DownloadISO(0xc000076b40, 0xc00042b280, 0x33, 0x1e3dd30, 0xf, 0xc0000b0080, 0x31, 0xc0002bf7c8, 0xc0002bf7c8)
        /go/src/github.com/docker/machine/libmachine/mcnutils/b2d.go:357 +0x17b
github.com/docker/machine/libmachine/mcnutils.(*B2dUtils).CopyIsoToMachineDir(0xc000076b40, 0xc0000b0080, 0x31, 0xc0004987b0, 0x7, 0xc0002bf8a0, 0x5758c4)
        /go/src/github.com/docker/machine/libmachine/mcnutils/b2d.go:461 +0x43c
github.com/docker/machine/drivers/virtualbox.(*b2dUtilsUpdater).CopyIsoToMachineDir(0x36c3468, 0xc0000ae060, 0x22, 0xc0004987b0, 0x7, 0xc0000b0080, 0x31, 0x16, 0x1b1da80)
        /go/src/github.com/docker/machine/drivers/virtualbox/misc.go:27 +0x76
github.com/docker/machine/drivers/virtualbox.(*Driver).CreateVM(0xc000287900, 0xc000092040, 0x28)
        /go/src/github.com/docker/machine/drivers/virtualbox/virtualbox.go:300 +0x92
github.com/docker/machine/drivers/virtualbox.(*Driver).Create(0xc000287900, 0x1eb2898, 0xc0002bfc00)
        /go/src/github.com/docker/machine/drivers/virtualbox/virtualbox.go:291 +0x36
github.com/docker/machine/libmachine/drivers/rpc.(*RPCServerDriver).Create(0xc00023fb40, 0x36c3468, 0x36c3468, 0x0, 0x0)
        /go/src/github.com/docker/machine/libmachine/drivers/rpc/server_driver.go:140 +0x6c
reflect.Value.call(0xc0000c94a0, 0xc00050e120, 0x13, 0x1e2e94b, 0x4, 0xc0002bff18, 0x3, 0x3, 0xc000152000, 0xd40010, ...)
        /usr/local/go/src/reflect/value.go:447 +0x468
reflect.Value.Call(0xc0000c94a0, 0xc00050e120, 0x13, 0xc0002bff18, 0x3, 0x3, 0x0, 0x0, 0x0)
        /usr/local/go/src/reflect/value.go:308 +0xab
net/rpc.(*service).call(0xc000528000, 0xc0000de460, 0xc000096040, 0xc000096050, 0xc00051aa00, 0xc00008ef60, 0x184b4c0, 0x36c3468, 0x16, 0x184b4c0, ...)
        /usr/local/go/src/net/rpc/server.go:384 +0x155
created by net/rpc.(*Server).ServeCodec
        /usr/local/go/src/net/rpc/server.go:481 +0x432

I installed toolbox2docker to C:\apps\dev\toolbox2docker and I tried these URLs:

file:///C/apps/dev/toolbox2docker/boot2docker.iso
file://C/apps/dev/toolbox2docker/boot2docker.iso
file:///C:/apps/dev/toolbox2docker/boot2docker.iso
file://C:/apps/dev/toolbox2docker/boot2docker.iso
file:///C:\apps\dev\toolbox2docker\boot2docker.iso
file://C:\apps\dev\toolbox2docker\boot2docker.iso

Any ideas?

In the meantime I am pointing --virtualbox-boot2docker-url directly to https://github.com/kaosagnt/boot2docker-xfs-ng/releases/download/20.10.7/boot2docker.iso

I don't know if it is possible, but would be great if you could change the installer to not enable these options by default:

20.10.3, clean install

`C:\Users\User>docker ps
panic: Invalid standard handle identifier: 4294967286

goroutine 1 [running]:
github.com/docker/cli/vendor/github.com/Azure/go-ansiterm/winterm.GetStdFile(0xf
ffffff6, 0xc00009c738, 0xb)
/go/src/github.com/docker/cli/vendor/github.com/Azure/go-ansiterm/winter
m/ansi.go:173 +0x1f3
github.com/docker/cli/vendor/github.com/moby/term/windows.NewAnsiReader(0xffffff
f6, 0xc00000000f, 0x20d5920)
/go/src/github.com/docker/cli/vendor/github.com/moby/term/windows/ansi_r
eader.go:34 +0x36
github.com/docker/cli/vendor/github.com/moby/term.StdStreams(0xc0002f61a0, 0xc00
04e5eb8, 0x1, 0x1, 0x0, 0x0)
/go/src/github.com/docker/cli/vendor/github.com/moby/term/term_windows.g
o:75 +0x1eb
github.com/docker/cli/cli/command.NewDockerCli(0x0, 0x0, 0x0, 0x19ba58c, 0x1b500
e0, 0xc000234180)
/go/src/github.com/docker/cli/cli/command/cli.go:473 +0x1a7
main.main()
/go/src/github.com/docker/cli/cmd/docker/docker.go:291 +0x4b`

This is rather a question that an issue.

Toolbox2Docker supports separate installations along with VirtualBox.
Currently I do use VirtualBox 6.x to be able to work with Toolbox2Docker.
I'm wondering if I can upgrade my VirtualBox to version 7.x (f.e. 7.0.8) and will be supported this VirtualBox version (7.0.8) by current Toolbox2Docker (23.0.5)?

Any help appreciated.

Made fresh install toolbox2docker (Toolbox2docker-20.10.17.exe) on Windows LTSC host.
After starting Docker Quickstart Terminal, it hangs on waiting for IP step.
On default VM console in VirtualBox I see error

Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)

See screenshot below:

Searched on stack overflow for this error, found recommendations to change Linux kernel (boot to previous kernel).

Please assist. Thanks.

Problem is noticed when docker-machine creates the initial VM under Windows host. It completely ignores bundled ISO image (but I have installed toolbox2docker in non-default location under D:\something, not sure if it matters), and tries to pull ISO from the now-archived boot2docker. It only allowed me to use the new xfs enabled ISO with --virtualbox-boot2docker-url option specified.

While patching and recompiling docker-machine is a very hefty price to pay for small problem like this. how about a few forewarning words in README?

Hello, this is not an issue but rather a question (don't know how to ask it directly):

I stumbled upon lack of space for docker images and containers. So, is it possible to increase virtual disk space after installation, or, at least somehow choose appropriate size before? 20 Gb is very small nowadays.

Thank you!