docker-archive/toolbox

docker volume mounts not working with boot2docker v19.03.0

Opened this issue · 17 comments

dhohengassner commented

Created a VM using docker-machine create today. It seems file volume mounts for docker containers are not working (mounted directories are empty). The reason seems to be that docker-machine grabs the latest boot2docker image - https://github.com/boot2docker/boot2docker/releases/tag/v19.03.0

Pinned the version now to v18.09.8 and mounts are working again.

This is easy to reproduce:

docker run --rm -it -v $PWD:/src --entrypoint sh alpine:latest
ls /src

Any help or fix is much appreciated!

Try-Parser commented

i found a little fix about this issue just dont use 19.03 Boot2Docker you can use that version 18.09.8 since 19.03 is 3 days ago the toolbox upgrading to the latest version..
and may i dont really know if i am correct since there is two version of Engine 18 and 19 maybe 18 is for toolbox and 19 for the hyper v.

docker-machine create --driver "virtualbox" --virtualbox-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v18.09.8/boot2docker.iso default
  • 👍9
mrhappytech commented

I have the same problem. Any version of 19.03.0 till today is with that error. It prevents use volumes with docker-compose. Re-installation of Docker Toolbox will not help in the case you will install it with v19.03.x. Because Docker Quickstart Terminal will always download new version of Boot2Docker you must unplug your internet for that moment and plug the cable back when it is waiting for IP address. Cheers.

  • 👍1
kainxspirits commented

I think it has been fixed on latest version (v19.03.1)

mrhappytech commented

Maybe, I re-installed the Boot2Docker yesterday and it was still doing that problem. So probably it is not fixed completely. With version v18.09.3 it is working OK.

kainxspirits commented

I mean, with the latest version of toolbox : https://github.com/docker/toolbox/releases/tag/v19.03.1.

Installers are not available yet, but you can easily build them by following those steps : https://github.com/docker/toolbox/tree/v19.03.1#building-the-docker-toolbox.

  • 👍1
  • 👎2
CollinChaffin commented

This is a big issue and the fix is simply install .1 yet for some reason after days it's the only version so far that installers have not be built hopefully they will be posted soon.

EDIT: Those build instructions are a joke all they show you how to do is create a new virtualbox machine, no pulling images etc. just create a new machine and "type make"?!? How was that doc even published.

EDIT2: The build instructions do not make any mention of what OS they need to be run on. I found a Photon host with git and all dev dependencies allowed me to then perform a git clone of the repo and THEN "simply run make" to produce the toolbox. :)

  • 👀1
theque5t commented

Suggestion from @Try-Parser resolved this for me

  • 👍1
weeix commented

I can still reproduce this issue with Docker Toolbox 19.03.1 and Boot2Docker 19.03.1:

ME@MYCOM MINGW64 ~/Documents/GitProj/flask_test (master)
$ ls app
app.py*  library/  requirements.txt  static/  templates/  uwsgi.ini

ME@MYCOM MINGW64 ~/Documents/GitProj/flask_test (master)
$ docker run --rm -it -v ${PWD}/app:/app alpine sh
/ # ls /app
/ #
horvathd commented

Updating VirtualBox to the latest version (6.0.10) solved this issue for me.

  • 👍2
  • ❤️1
blacktear commented

thinks! @horvathd @dhohengassner
Updating VirtualBox to the latest version (6.0.10) solved this issue for me.

fenicento commented

thinks! @horvathd @dhohengassner
Updating VirtualBox to the latest version (6.0.10) solved this issue for me.

Same here, 6.0.10 solves the issue. Any chance that it will be included in a new release soon?

guillaumerose commented

Hello,

Yesterday @ulrich upgraded VirtualBox and made some tests. It seems to work fine for him now. So I merged the PR. Could you double-check and try this build ? If it's ok, I will do the release next week.

https://download-stage.docker.com/desktop/toolbox/844/DockerToolbox.pkg
https://download-stage.docker.com/desktop/toolbox/844/DockerToolbox.exe

Thanks!

  • 🎉1
fenicento commented

Hello,

Yesterday @ulrich upgraded VirtualBox and made some tests. It seems to work fine for him now. So I merged the PR. Could you double-check and try this build ? If it's ok, I will do the release next week.

https://download-stage.docker.com/desktop/toolbox/844/DockerToolbox.pkg
https://download-stage.docker.com/desktop/toolbox/844/DockerToolbox.exe

Thanks!

I'm having an issue when running docker quickstart terminal. When creating and running the virtual machine, I get

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2 ' (VERR_INTNET_FLT_IF_NOT_FOUND).

this seems related to this bug, and disabling and enabling again the adapter does the job. Apart from this, volumes get mounted correctly and everything seems to work fine for now.

  • 👍1
ulrich commented

OK, thank you for your feedback. @guillaumerose and I will plan the release this week so.

fenicento commented

OK, thank you for your feedback. @guillaumerose and I will plan the release this week so.

@ulrich, any news?

Yuriy-Svetlov commented

I am experiencing a problem on VirtualBox version 6.0.14

BoGnY commented

The solution is deleting all "VirtualBox Host-Only Ethernet Adapter" in network cards' section in the "Device manager" of Windows 10 Control Panel 👍