Ok, that shows the change from Tiny Core Linux (TCL) 12.x to TCL 13.x . I need to find time to extract the TCL boot files and compare any differences.

from toolbox2docker.

I changed "default" VM settings.
Set 2048 RAM and checked AMD-V box.
That helped.

from toolbox2docker.

A new version of docker-machine is available for testing. All the drivers have been bumped to 2048MB as default.

https://github.com/kaosagnt/docker-machine/releases/tag/v0.16.2-gitlab.18-t2d.4

from toolbox2docker.

I have managed to reproduce the issue in a Windows 7 pro virtual machine that I have for testing, so it is not limited to windows 10 and above.

After rolling a newer Boot2docker ISO with the latest Kernel 5.15.50 I am able to create and boot the VM successfully.

Running pre-create checks...
(default) Boot2Docker URL was explicitly set to "file://localhost/Users/ianm/.docker/machine/cache/boot2docker.iso" at create time, so Docker Machine cannot upgrade this machine to the latest version.
Creating machine...
(default) Boot2Docker URL was explicitly set to "file://localhost/Users/ianm/.docker/machine/cache/boot2docker.iso" at create time, so Docker Machine cannot upgrade this machine to the latest version.
(default) Downloading C:\Users\ianm.docker\machine\cache\boot2docker.iso from file://localhost/Users/ianm/.docker/machine/cache/boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
(default) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: C:\Program Files\Toolbox2docker\docker-machine.exe env default
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Running tcp://192.168.99.102:2376 v20.10.17

ianm@krista-win7-2 MINGW64 ~/Desktop
$ docker-machine.exe env default
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.102:2376"
export DOCKER_CERT_PATH="C:\Users\ianm.docker\machine\machines\default"
export DOCKER_MACHINE_NAME="default"
export COMPOSE_CONVERT_WINDOWS_PATHS="true"

Run this command to configure your shell:

eval $("C:\Program Files\Toolbox2docker\docker-machine.exe" env default)

ianm@krista-win7-2 MINGW64 ~/Desktop
$ docker-machine.exe ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Running tcp://192.168.99.102:2376 v20.10.17

ianm@krista-win7-2 MINGW64 ~/Desktop
$ docker-machine ssh default
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
______ o /
\ \ /
_______/

| |__ ___ ___ | ||__ \ | | ___ | | _____ _ __
| ' \ / _ \ / _ | __| __) / ` |/ _ \ / | |/ / _ \ '|
| |) | () | () | | / / (| | () | (| < / |
|_./ _/ _/ __|_,|_/ _||____||

boot2docker - VirtualBox GA 6.1.34 | OpenVMTools 11.2.5.26209
Docker 20.10.17 | Kernel 5.15.50-boot2docker | TCL (13.1)
Built by kaosagnt Sun Jun 26 10:08:47 AEST 2022
docker@default:~$

I'll be load a newer Boot2docker ISO to the 20.10.17 Github release page shortly.
https://github.com/kaosagnt/boot2docker-xfs-ng/releases/tag/20.10.17

You will need to delete the files for the broken VM before trying to create a new one.

C:\users{USERNAME}.docker\machine\machines\default

just delete the "default" directory.

A newer ISO will be downloaded when you are creating the VM and hopefully fixes this problem.

from toolbox2docker.

1. Removed directory %USERPROFILE%\.docker\machine\machines\default
2. Started Docker Quickstart Terminal
3. In terminal screen I noticed that boot2docker.iso was downloaded.

This file has checksums:
SHA-1: c0f8748f64c7e2fe03a311b77b6d17e58dd77004
SHA-256: 7ee862683b6981d91d8d7e14cd87aca5e240c112a600d8bfb38795addefef426

4. The error occurred again.

Probably you didn't yet updated boot2docker.iso?

from toolbox2docker.

That's the correct checksum for the ISO with the 5.15.50 Kernel.

I suspect that since Virtualbox 6.1.34 has had 2 releases (6.1.34 / 6.1.34a) that is the likely suspect causing the issue.

You could try uninstalling VirtualBox and installing a older release like 6.1.32 and see what happens.
Don't forget to remove the borked default virtual machine as per your step one again.

from toolbox2docker.

On a fresh Windows 10 (this Windows 10 installed inside Oracle Virtual Box) I've installed:

1. Oracle Virtual Box from VirtualBox-6.1.32-149290-Win.exe
2. Git from Git-2.37.1-64-bit.exe
3. Docker from Toolbox2docker-20.10.17.exe (during setup, Virtual Box and Git options was unchecked since I want to use one installed before).

This error occurred again.

Could it be related to a XFS filesystem on ISO image (kernel somehow cannot load drivers for it or something like this).
I can try to start this using non XFS ISO (if such exists and if you can provide some information how to override ISO path when Docker Toolbox is starting). One option probably would be to override path to https://github.com/kaosagnt/boot2docker-xfs-ng overriding ISO file with no XFS filesystem on it.
I'm not an expert in Linux, XFS etc and this is just my assumption based on fact, that on the same Oracle Virtual Box, Git and my host OS if I use DockerToolbox-19.03.1.exe it works fine.

from toolbox2docker.

I also made such test:

1. Created in Oracle Virtual Box brand new VM (Other Linux 64 bit), booting from your modified ISO (downloaded from https://github.com/kaosagnt/boot2docker-xfs-ng/releases/download/20.10.17/boot2docker.iso): the result was error like I wrote above
2. In the same VM I switched boot from a ISO file, downloaded from https://github.com/boot2docker/boot2docker/releases/download/v19.03.12/boot2docker.iso: as a result Linux booted normally without any errors.

I'm not expert, but may it be the case that Linux on your modified ISO lacks some drivers or settings to properly handle this XFS (AFAIK in this linux ISO used EXT4FS).

from toolbox2docker.

Also this topic may be useful: https://unix.stackexchange.com/questions/414655/not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block0-0

from toolbox2docker.

"I'm not expert, but may it be the case that Linux on your modified ISO lacks some drivers or settings to properly handle this XFS (AFAIK in this linux ISO used EXT4FS)."

Unlikely as I use this under VMWare Fusion on macOS X on a daily basis with no issues.

It is likely to be some issue with the boot loader and virtualbox. With regard to the differences between the boot2docker iso with docker toolbox and the boot2docker iso used here, there are lots. At least 2-3 tiny core linux releases just for one. It make take a few days as I don't have a win 10 setup to diagnose this at present.

from toolbox2docker.

Virtualbox 6.1.34 on macOS X

Running pre-create checks...
(default) Default Boot2Docker ISO is out-of-date, downloading the latest release...
(default) Latest release for github.com/kaosagnt/boot2docker-xfs-ng is 20.10.17
(default) Downloading /Users/ianm/.docker/machine/cache/boot2docker.iso from https://github.com/kaosagnt/boot2docker-xfs-ng/releases/download/20.10.17/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Creating machine...
(default) Default Boot2Docker ISO is out-of-date, downloading the latest release...
(default) Latest release for github.com/kaosagnt/boot2docker-xfs-ng is 20.10.17
(default) Downloading /Users/ianm/.docker/machine/cache/boot2docker.iso from https://github.com/kaosagnt/boot2docker-xfs-ng/releases/download/20.10.17/boot2docker.iso...
(default) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(default) Copying /Users/ianm/.docker/machine/cache/boot2docker.iso to /Users/ianm/.docker/machine/machines/default/boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Found a new host-only adapter: "vboxnet1"
(default) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env default
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v20.10.17

screenshot:

from toolbox2docker.

I've tested once again on fresh laptop with Windows 10 LTSC installed. Got the same error. Probably this is a some VirtualBox on Windows bug.

Could I ask you (of course if you have time and if it is possible) to prepare boot2docker ISO file not with XFS, but with Ext4FS on it just for test? Or if it already exists, could you point me on it? Thanks!

from toolbox2docker.

I have installed a win 10 VM and had it fail. I have an ISO with debugging turned on and that works, so I can only assume that a race condition is present under Virtualbox + win 10 that doesn't show itself elsewhere and the addition of printing more to the console is enough to slow down the process to succeed. I haven't had to to look further into the issue yet.

If you create a vm as you did with the old Docker Toolbox ISO, you can just copy the Toolbox2docker ISO over into the ${User}.docker\machine\machines\default\boot2docker.iso directory (substitute the name you called the vm for default if you called it something else). The Toolbox2docker ISO will work with an already existing ext4 filesystem.

from toolbox2docker.

Could you please share this ISO with debugging turned on file, I'll try to test it. Thanks!

from toolbox2docker.

The ISO even zipped, is too large to attach to this ticket and I don't currently have anywhere for you to fetch it.

If you build the ISO yourself from https://github.com/kaosagnt/boot2docker-xfs-ng

Look for the lines in the Dockerfile and uncomment the next line after
temporary boot debugging aid
RUN sed -i '2i set -x' etc/init.d/tc-config

This will give a bit more output to the console while booting.

from toolbox2docker.

I have just experienced the same problem: Windows 10, VirtualBox 6.1.36, boot2docker 20.10.17-xfs. I have made the following experiment. A new vm was created with just one storage device - boot2docker.iso. The youngest version which could be booted was 20.10.12-xfs. Maybe it could help you.

from toolbox2docker.

toolbox2docker v.20.10.12 works!

I turned off the host network to disallow downloading of the newest version of boot2docker. To be on the safe side, I put boot2docker.iso v.20.10.12-xfs to %USERPROFILE%\.docker\machine\cache\

from toolbox2docker.

@rashid-test Thanks for the information.
Also tried steps your described and everything worked just fine.

from toolbox2docker.

@rashid-test Thank you very much.
Also helped me.
In my case it was enough to set the amount of RAM to 1536 MB. Maybe it would work also with 1152 MB - just not tested. The box "Enable Nested VT-x/AMD-V" is disabled and unchecked on my hardware, but the toolbox2docker works with your tip without any problem!

from toolbox2docker.

Enable Nested VT-x/AMD-V should make no difference as this is a pass through to allow running a hypervisor on the Boot2docker VM.

These are the default memory setting for the drivers in docker-machine. I'll probably crank all the 1024 to 2048MB as the default for all.

drivers/vmwarefusion/fusion_darwin.go: defaultMemory = 1024
drivers/softlayer/driver.go: defaultMemory = 1024
drivers/vmwarevsphere/vsphere.go: defaultMemory = 2048
drivers/virtualbox/virtualbox.go: defaultMemory = 1024
drivers/vmwarevcloudair/vcloudair.go: defaultMemory = 2048
drivers/hyperv/hyperv.go: defaultMemory = 1024

from toolbox2docker.

Toolbox2docker 20.10.19 is now available

https://github.com/kaosagnt/toolbox2docker/releases/tag/20.10.19

from toolbox2docker.

Closing as it seems there are no issues logged for the last 4 releases.

from toolbox2docker.