4 ms·

From someone who has wasted many hours trying to get B2D working, I have ended up using https://github.com/codekitchen/dinghy https://github.com/codekitchen/din

by shlant 11y ago

From someone who has wasted many hours trying to get B2D working, I have ended up using https://github.com/codekitchen/dinghy https://github.com/codekitchen/dinghy Easier to use, more reliable and some nice features like the OPs .docker DNS and NFS shares. The maintainer is very responsive and I recommend it to anyone who is struggling with docker on OSX.

spike021 11y ago
I don't have much use for Docker on my personal OSX computer, but whenever I've tried to get things running smoothly on there for pet projects, B2D was such a pain and either wouldn't work at all, or would be pretty awful to get set up properly.
STRML 11y ago
After seeing this article, I just migrated from Dinghy to Dlite. I saved about 5GB of disk space, got much faster VM startup time and basically no hassle. It was a cinch to work my docker-compose startup into a LaunchAgent and now I finally have all my services running on boot. I highly recommend giving it a shot; my eyes nearly popped when I saw how quickly it downloaded and started the VM (must have been all of a 10MB download).
- Pym 11y ago
  As a Dinghy user too, thank you! I will give a shot at Dlite right now :)
adamsea 11y ago
Out of curiousity, did you try docker-machine (the docker toolbox)? I have found that to be fairly straightforward, though I had not used B2D previously.
- yeukhon 11y ago
  To be clear on adamsea's point, docker-machine is now the replacement for B2D and is also officially supported.
Myrmornis 11y ago
In my experience the OSX tools for docker work absolutely fine. If you've got in a bad state, completely uninstall all existing docker-related stuff, `brew update` and `brew install docker-machine`. The article sounds like a fun personal project, but I definitely don't see inconvenience on OSX being a justification. If shell commands are too much to type then create aliases. The VM's IP doesn't seem to change; add an entry in /etc/hosts mapping it to something like "docker-machine". I don't understand the people in this thread complaining that OSX support is, e.g., "lackluster". The docker containers don't run on OSX so it's very nice that there's an OSX client that works perfectly as far as I can tell.
- fishnchips 11y ago
  My experience is that the toolchain works fine but performance is lacking, especially when sharing many files between the OS X host and the Docker container.
bovermyer 11y ago
I used to use dinghy, but setting it up required a lengthy process. Because I'm trying to migrate my department to Docker, I wanted to streamline the onboarding process, and ended up blowing away everything and switching back to Docker Toolbox. Haven't had any problems since, and it's been easier to get people started.

by shlant 11y ago

spike021 11y ago

I don't have much use for Docker on my personal OSX computer, but whenever I've tried to get things running smoothly on there for pet projects, B2D was such a pain and either wouldn't work at all, or would be pretty awful to get set up properly.

STRML 11y ago

After seeing this article, I just migrated from Dinghy to Dlite. I saved about 5GB of disk space, got much faster VM startup time and basically no hassle. It was a cinch to work my docker-compose startup into a LaunchAgent and now I finally have all my services running on boot. I highly recommend giving it a shot; my eyes nearly popped when I saw how quickly it downloaded and started the VM (must have been all of a 10MB download).

Pym 11y ago
As a Dinghy user too, thank you! I will give a shot at Dlite right now :)

adamsea 11y ago

Out of curiousity, did you try docker-machine (the docker toolbox)? I have found that to be fairly straightforward, though I had not used B2D previously.

yeukhon 11y ago
To be clear on adamsea's point, docker-machine is now the replacement for B2D and is also officially supported.

Myrmornis 11y ago

In my experience the OSX tools for docker work absolutely fine. If you've got in a bad state, completely uninstall all existing docker-related stuff, `brew update` and `brew install docker-machine`. The article sounds like a fun personal project, but I definitely don't see inconvenience on OSX being a justification. If shell commands are too much to type then create aliases. The VM's IP doesn't seem to change; add an entry in /etc/hosts mapping it to something like "docker-machine". I don't understand the people in this thread complaining that OSX support is, e.g., "lackluster". The docker containers don't run on OSX so it's very nice that there's an OSX client that works perfectly as far as I can tell.

fishnchips 11y ago
My experience is that the toolchain works fine but performance is lacking, especially when sharing many files between the OS X host and the Docker container.

bovermyer 11y ago

I used to use dinghy, but setting it up required a lengthy process. Because I'm trying to migrate my department to Docker, I wanted to streamline the onboarding process, and ended up blowing away everything and switching back to Docker Toolbox. Haven't had any problems since, and it's been easier to get people started.