81–89 of 89 posts
Pretty cool trick to make the OS X docker hacks feel transparent. I've been tempted into getting a Linux laptop just because using Docker on OS X feels so hacky.
Linux works quite well on Macbooks. No need to buy more hardware.
From someone who has wasted many hours trying to get B2D working, I have ended up using 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.
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…
Earlier quoted context omitted.
Been using Linux on my work macbooks since 2009. There are some bumps involved, but it works really well on the awesome Apple hardware.
How's the battery life?
if flash starts, i get less than half. (using archlinux on a mid-2012 mbp)
From someone who has wasted many hours trying to get B2D working, I have ended up using 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.
Haven't had any problems since, and it's been easier to get people started.
Earlier quoted context omitted.
Been using Linux on my work macbooks since 2009. There are some bumps involved, but it works really well on the awesome Apple hardware.
I dual-booted Mint on my 2011 MBA the other week and it was a nasty experience. I feel like Linux users have low standards, or maybe I've been away too long. Here's four things I found immediately: 1. The fans don't automatically react to temperature without a background daemon (?!). 2. Multi-touch trackpad support is terrible. The default synaptic driver can't handle you resting your thumb on the bottom of the track…
1. I currently don't have a problem with that (the fans/temperature management). In my seven years of running Ubuntu on Macbooks, I've run into that in the past, but it's been a while. 2. I've never been a 'full' OSX user, but I understand that they are doing a lot of very nifty things with the touch pad, not surprisingly. My experience with the touchpad under Ubuntu is generally not as good as under OSX. 3. Can't comment on this one 4. As described elsewhere.
For most people, I would not recommend running any Linux flavor on a Macbook. I am a 'UNIX guy' for decades now. Hell, I even run a minimalistic windows manager (http://www.6809.org.uk/evilwm/)
For me, the upsides outweigh the downsides. I'm pretty sure that's not the case for most people though.
And if you really need docker-lite- you do not need to write it in go, just do
Run that once (do sudo or any other crazy stuff):
``` echo $(docker-machine ip dev) local.docker >> /etc/hosts ```
Add that to `.bashrc`
``` eval $(docker-machine eval dev) ```
Earlier quoted context omitted.
Same goes for Cisco AnyConnect VPN. Updating the routing table seems to temporarily fix it, but it would be nice not to hack around it to get it to work.
> Updating the routing table seems to temporarily fix it, can you share a link ? thanks
Earlier quoted context omitted.
docker-machine automates setting up a VM running Docker. There's nothing manual about it (besides running "docker-machine create dev" or whatever)
Docker-machine drove me up a wall. Getting file sharing to work so I could use my nice Mac editors on my in-docker code was a huge waste of time and effort. Docker-machine was just another one of those crappy half-measures that keep Mac owners struggling to find a way to make Docker graceful. I was also motivated by bringing on new team members who were on Windows rather than Macs. Vagrant works fine and transparentl…
This is a simple alternative than the solution I wrote about here: https://allysonjulian.com/setting-up-docker-with-xhyve/ which uses docker-machine-driver-xhyve (https://github.com/zchee/docker-machine-driver-xhyve).
I've been trying to figure out how to deal with the env variables used by docker, and used a workaround ~/.profile (https://gist.github.com/astrohckr/efceb07887225cbc2ba2). Like the OP, running eval in every terminal session makes me a bit concerned as well.
I'll give dlite a Go.