[deleted]
Announcing Docker ToolBox
51–60 of 73 posts
Re: Announcing Docker ToolBox
#52Does anyone have any idea how to get the Docker Quickstart Terminal app to use iterm2/zsh instead of Terminal/bsh?
If you look at the contents of the .app, you can edit main.scpt in AppleScript Editor, but it's really just doing two things, creating the VM if necessary:
docker-machine create -d virtualbox --virtualbox-memory 2048 default
and populating environment variables for docker:
eval $(docker-machine env default)
Passing --shell zsh to docker-machine env doesn't seem to change its output. Does zsh understand commands like the following?
export DOCKER_MACHINE_NAME="default"
Re: Announcing Docker ToolBox
#53Nice one. However, VirtualBox's shared-folder support is so god-awfully slow, that here at work we all swapped out the regular boot2docker setup for boot2docker-xhyve[0] which is so much faster at nearly everything that it's not even a comparison. Now, with ailispaw's dockeroot-xhyve you can even get a VM root image that can be grown on the fly, so you never run out of space on your VM when building large Docker imag…
Let me chime in and say that getting rid of VirtualBox and moving to xhyve would be amazing. I was really sad when this PR was closed: https://github.com/docker/machine/pull/1358#issuecomment-126...
It will happen :) Xhyve is pretty new (and only works on pretty recent OSX installs), but we are also feeling the pain of the default vbox install and really want to fix it.
Re: Announcing Docker ToolBox
#54Nice one. However, VirtualBox's shared-folder support is so god-awfully slow, that here at work we all swapped out the regular boot2docker setup for boot2docker-xhyve[0] which is so much faster at nearly everything that it's not even a comparison. Now, with ailispaw's dockeroot-xhyve you can even get a VM root image that can be grown on the fly, so you never run out of space on your VM when building large Docker imag…
What should I use in place of docker compose?
Re: Announcing Docker ToolBox
#55Sadly no support for Parallels.
The docker team completely ignored the great work the parallels team put into creating a parallels driver instead telling them to wait for the plugin architecture to be finished. Reference: https://github.com/docker/machine/pull/939
That is a bit of a bummer, but do I understand correctly that the driver only supports a yet-to-be-released version of Parallels?
Re: Announcing Docker ToolBox
#56Earlier quoted context omitted.
Docker Machine alone knocks out the entire list of hosts you laid out: https://docs.docker.com/machine/ For more sophisticated scheduling needs there is http://www.replicated.com/ , https://cloud.google.com/container-engine/ , and https://aws.amazon.com/ecs/ Related to what you say about "don't VM's solve this problem?" is a project called https://hyper.sh . They're coming at it from the angle that if VM's can boot r…
So docker machine will create an image for that particular host (AWS/DO/GC...) and create a docker image on TOP of that, correct? It solves the problem of me configuring multiple hosts, but there's still an extra OS layer in there, isn't it?
Docker machine creates and manages VMs, then you can run any number of containers on those VMs.
Re: Announcing Docker ToolBox
#57Nice one. However, VirtualBox's shared-folder support is so god-awfully slow, that here at work we all swapped out the regular boot2docker setup for boot2docker-xhyve[0] which is so much faster at nearly everything that it's not even a comparison. Now, with ailispaw's dockeroot-xhyve you can even get a VM root image that can be grown on the fly, so you never run out of space on your VM when building large Docker imag…
> In addition, I'd never recommend Docker Compose to web developers that rely on databases, as quirks with it have caused many a volume-only container to be destroyed and rebuilt, thus defeating the purpose.
Can you point me in the direction of a bug report or a more concrete example? I'd like to make sure we follow up.
Re: Announcing Docker ToolBox
#58You can stand up Joyent's Triton[1] service locally for development with Docker. The hardware is very affordable, and I think that they have a very underrated product on their hands.
[1] https://www.joyent.com/blog/spin-up-a-docker-dev-test-enviro...
Re: Announcing Docker ToolBox
#59Earlier quoted context omitted.
Let me chime in and say that getting rid of VirtualBox and moving to xhyve would be amazing. I was really sad when this PR was closed: https://github.com/docker/machine/pull/1358#issuecomment-126...
It will happen :) Xhyve is pretty new (and only works on pretty recent OSX installs), but we are also feeling the pain of the default vbox install and really want to fix it.
That's great news, Solomon - thanks :)
Re: Announcing Docker ToolBox
#60Hi all. We know the experience of using Docker on OSX is not perfect today. The default virtualbox configuration for file sharing is slow and buggy. You need to use 3 different CLIs (`docker`, `docker-machine`, `docker-compose`) which are not well integrated. 3d-party clients need to reimplement everything themselves. The standard clients are not configurable or customizable enough.
We plan on solving all of this. There is a new team at Docker focused entirely on solving "Developer Experience" problems. This initial release of Toolbox is a starting point: a convenience packaging of existing tools. But we are going to update it with more and more improvements.
In short: we are going to work hard to make the experience of using Docker to develop on Mac OS X (and Windows) much, much better.