3 ms·
It solves a very specific problem - using Docker on OS X is a giant pain. It's pretty easy on something like Ubuntu, but for Mac the typical solution involves
by notduncansmith 12y ago
It solves a very specific problem - using Docker on OS X is a giant pain. It's pretty easy on something like Ubuntu, but for Mac the typical solution involves Vagrant + a VM, so startup times are slow, it eats a lot of memory and CPU, etc.
- StavrosK 12y agoOh, thanks, I thought it was an image manager (which I could use). I guess you'd have a problem with Docker on OS X, given the BSD-based kernel...
- mchiang 12y agoKitematic can be used as an image manager.
- bboreham 12y agoIt looks like Kitematic uses VirtualBox, a VM. Aside from the GUI, how does it differ from Boot2Docker, which is what the Docker web site tells you to use on a Mac?
- mchiang 12y ago- Automatically creates a folder under ~/Kitematic for each Volume. - One click NSEnter into any container. - Any container can be accessed at <container_name>.dev (automatically sets up a DNS for you, so you can connect a database too using that URL). We're really just trying to make Docker easier to use for Mac right now.
- mrinterweb 12y agoI disagree that "using Docker on OS X is a giant pain". I don't really see how this is more than a GUI that works with boot2docker and docker. Kitematic appears to be using boot2docker under the hood. I think using boot2docker is very simple. Once boot2docker is running, as far as I can tell, using docker is the same experience people have on linux.
- shabble 12y agomounting host directories into containers with -v is one place b2d definitely hurts more than running on linux directly. The options appear to be: 1. Don't do that 2. Mount something via samba into the b2d vm, then -v it into your container 3. Use virtualbox directory sharing (which won't work properly/at all)