Live data from Hacker News

Announcing Docker ToolBox

blog.docker.com

31–40 of 73 posts

Re: Announcing Docker ToolBox

#31
post #28
post #26

Earlier quoted context omitted.

Thanks. Any idea about this? > ...if my application creates a fork(), will the container be unable to handle scheduling of the additional process?

Forking works fine.

Hmm... if there's no kernel, who manages the process scheduling?

Re: Announcing Docker ToolBox

#32
post #8

This looks cool, although for the Windows install I'd have hoped that there would be an option to integrate Hyper-V with it instead of Virtualbox, seeing as Hyper-V is available on all Windows 8.1/10 pro/enterprise systems, and having multiple virtualization platforms active on a system is generally a bad idea...

There is a hyper-v driver for docker-machine. You can use it like so:

    docker-machine create -d hyper-v vmname

Re: Announcing Docker ToolBox

#33
post #25
post #23

Earlier quoted context omitted.

Ok, this is starting to clear things up for me. When you say that it runs a single process by design, does it mean that if my application creates a fork(), the image will be unable to handle scheduling of the additional process? Let's say I have an application that talks to MySQL. What is the right way in docker? Should I have two separate docker images, one running the application and the other running MySQL, with t…

> Should I have two separate docker images, one running the application and the other running MySQL, with them talking to each other across the host OS? Yes. > Or can they be configured in a single docker image? They can , but it's an anti-pattern and there are hurdles to overcome if you try managing processes using an init system.

People differ on this point. Discourse, for example, ships a single Docker container which runs the Rails-based webapp, a database server (PostgreSQL), and a key-value store (Redis). They have been using this same setup in production for quite a while now.

Re: Announcing Docker ToolBox

#34
post #31
post #28

Earlier quoted context omitted.

Forking works fine.

Hmm... if there's no kernel, who manages the process scheduling?

It uses the host OS kernel, which is why its limited to a subset of Linux host machines.

Honestly Docker is the epitome of the incorrect understanding of "DevOps".

Re: Announcing Docker ToolBox

#36
post #3

Nice 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…

Has anyone tried VMWare fusion to run a Docker host VM? Virtualbox shared folders are unusable for my purpose (compiling software on Linux).

> Has anyone tried VMWare fusion to run a Docker host VM?

If you're considering Fusion I'd suggest taking a look at AppCatalyst[1] instead (N.B. I work at VMware, but not on AppCatalyst).

[1] http://blogs.vmware.com/cloudnative/vmware-appcatalyst/

Re: Announcing Docker ToolBox

#38
post #11

I really, really, don't understand the docker fixation, but maybe I'm missing something. The most important function of docker, IMHO, is that it standardizes the creation of a VM using Virtualbox across platforms. Unless Amazon AWS, DigitalOcean, GoogleCompute, etc. allow a docker image (aka a VirtualBox image) to run directly on their base virtualization platform (without me putting together an AMI or whatever on th…

I think you are confusing Docker with Vagrant. Vagrant provisions VM, Docker is about containers (which may or may not run on a VM)

Re: Announcing Docker ToolBox

#40

Earlier quoted context omitted.

Has anyone tried VMWare fusion to run a Docker host VM? Virtualbox shared folders are unusable for my purpose (compiling software on Linux).

Yes, and I think its much worse in terms of reliability. When I save a file (say a Gemfile), sometimes only half of it shows up inside the container. Anybody know what would cause VMWare Fusion (or any VM for that matter) to behave this way?

I run into this. Files are only partially synced.

You end up with broken code. If you are lucky it has a syntax error. If you are not lucky you get mysterious bugs.

The work around is to go back and try re-editing the file to retrigger a sync.

There are lots recommendations to try Fusion over Vbox but I think this issue makes it a wash.

Post reply on HN