Live data from Hacker News

Docker 0.8: Quality, new builder features, btrfs, OSX support

blog.docker.io

111–120 of 128 posts

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#111
post #73

Earlier quoted context omitted.

Try here: http://www.docker.io/learn_more/

nope, I still don't get it. > Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere. Like an internet browser for executables ? I don't understand how can this be useful...

it's like a vm, but it's much lighter (runs faster / uses less cpu, memory and disk). it does that by re-using the host kernel. so you are forced to have the same kernel in your client as in your host, and that has to be linux 64 bit.

an example of where it's useful, for me, is in system integration tests. unit tests are designed to run without changing the machine they run on, but for system integration you need to build and install and configure and run a system. so you really need something like a vm. docker gives you that isolation, but with lower overheads.

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#113
Awesome release, especially since I can now use Docker on OS X without having to boot up a full Ubuntu VM through Vagrant.

If anyone else is using Boxen, I packaged up a quick Puppet module to get up and running with Docker on OS X: https://github.com/morgante/puppet-docker

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#116

So what's the solution for 'root inside a docker container is root on the host'? We'd like to ship a set of utilities as a docker container, but unless the sysadmin gives everyone 'sudo' privileges on the server (unlikely and insecure), they can't run the container and its utilities. Any advice?

user namespaces will solve this. lxc in ubuntu 14.04 already supports docker in user lxc, ie. no root needed.

add silly disclaimer.. yes docker has some notion of portable containers plugins, but it uses lxc atm, and the feature is in lxc upstream.

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#117
post #4

Glad to hear OS X has official support. I jumped into Docker for the first time last week and have a burning unresolved question for those using boot2docker. What is your development workflow? I am working on a Rails app, so my instinct is to have a shared folder between OS X and boot2docker, but afaik this is not supported as boot2docker doesn't support VirtualBox guest extensions.

Hi Matt, you are not alone :) It turns out that shared folders are not a sustainable solution (independently of whether boot2docker supports them), so the best practices are converging towards this: 1) While developing, your dev environment (including the source code and method for fetching it) should live in a container. This container could be as simple as a shell box with git and ssh installed, where you keep a te…

I would really be interrested in details on how to connect the filesystem between OSX and docker/linux via 9p.

What would be the recommended way? How to install the required software on either system. Host on OSX or on Linux?

On a recent Linux it seems like a modprobe 9p activates the required module and then a mount -t 9p serverIP /mountpoint seems to do the trick.

But what about the OSX side?

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#118
post #41

Earlier quoted context omitted.

and I'm always told that macs are superior because they "just work," hmm

That's marketing. They have the same number of problems as all other OSes and computers. I have found a higher percentage of Windows users to know where to look for system messages compared to the number of Mac users who know how to look for system messages. Perhaps it is because I have met more Windows users or perhaps they need to look these things up more...? But in any case, you meet more "hardcore" Windows users…

Not sure why the downvotes here! It isn't an anti-Apple rant, it's true! My day job involves writing OSX software on a Mac Pro and at home my only machine is a MacBook Pro, where I funnily enough write OSX software!

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#119
post #46
post #4

Earlier quoted context omitted.

Hi Matt, you are not alone :) It turns out that shared folders are not a sustainable solution (independently of whether boot2docker supports them), so the best practices are converging towards this: 1) While developing, your dev environment (including the source code and method for fetching it) should live in a container. This container could be as simple as a shell box with git and ssh installed, where you keep a te…

from my experience samba, nfs are awfully slow when working with big projects. When you use an IDE or Editor that indexes all files for fast search and Intellisense, using NFS/Samba is problematic imo. Thats why i like the vagrant approach, i can edit the code with all the speed of my local tools, and just the vm accesses them through NFS which is fast enough for serving requests in 1-2s.

In your experience are bfs and samba really slow on a virtual network? I have trouble imagining that it would sliw things down enough to be a problem.

Re: Docker 0.8: Quality, new builder features, btrfs, OSX support

#120

why is osx support necessary on the path to 1.0? i'd rather have a simple, small, 1.0 release i can trust than all these "bells and whistles".

It's not necessary and we didn't go out of our way to get it. We just happened "for free" as a result of writing portable code, a clean client-server architecture and the appearance of the boot2docker project in the community.
Post reply on HN