Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

blog.docker.io

Post reply on HN
Print view View original

31–40 of 128 posts

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

#31

Post by bstar77 »

shykes wrote: post #4
mattbessey wrote: post #2

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…

Thanks for taking the time to write this. I've hit a major wall in figuring out the best workflow for this exact scenario. Good to finally hear an official suggestion on the matter. I've been depending on shared directories, so I'll definitely be experimenting with network filesystems.

As Docker evolves, it would be great to have some kind of official resource to get suggestions for optimal workflows as new features become available (the weekly docker email is my best resource right now). Searching the internet for info has been a huge chore as most of the resources (including the ones hosted by docker.io) are woefully out of date.

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

#32

Post by tksb »

shykes wrote: post #4
mattbessey wrote: post #2

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…

Thank you for this. I found it extremely helpful.

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

#34

Post by zobzu »

stesch wrote: post #33

Is Docker a good way to bring more security on a server with a few different websites? Separating the sites from each other and run nginx as a proxy in front of them? What's the overhead?

its not as good as using separate vms, but has arguably lower overhead

also, its not really docker doing that, its LXC. Docker is an API around it.

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

#35

Post by ecnahc515 »

shykes wrote: post #4
mattbessey wrote: post #2

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…

This should be a blog post or tutorial or guide on the documentation page. It would be really helpful to have guidance on how to do development work flow using docker while avoiding bad practices like shared volumes.

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

#36

Post by FireBeyond »

stesch wrote: post #33

Is Docker a good way to bring more security on a server with a few different websites? Separating the sites from each other and run nginx as a proxy in front of them? What's the overhead?

Yes, it is. It’s atop LXC (Linux Containers), which - oversimplified - is process namespacing, jails, etc.

There’s near zero overhead, because there’s no virtualization.

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

#37

Post by FireBeyond »

ecnahc515 wrote: post #35
shykes wrote: 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…

This should be a blog post or tutorial or guide on the documentation page. It would be really helpful to have guidance on how to do development work flow using docker while avoiding bad practices like shared volumes.

Seconded. My biggest stumbling block with Docker at the moment is “best practices”, as I work on coming up with a Docker Dev Ecosystem (for myself and for a team).

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

#38

Post by phaer »

lengads wrote: post #28
tianon wrote: post #21

Earlier quoted context omitted.

Or even bare metal. Personally, I extract the kernel and initrd and use it directly via PXE.

Is that to say that you.. wait, what are you doing?

I guess s/he owns a second machine and boots boot2docker over the network (PXE = https://en.wikipedia.org/wiki/Preboot_Execution_Environment ) without installing anything on the second machine.

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

#39

Post by crosbymichael »

joeshaw wrote: post #25

Was the OS X binary built without cgo? I can't seem to access containers in private https registries: $ docker login https://registry.example.com 2014/02/05 14:36:20 Invalid Registry endpoint: Get https://registry.example.com/v1/_ping: x509: failed to load system roots and no roots provided The hostname in question has a valid SSL certificate. I encountered a similar problem in the past with Go built from homebrew[1]…

Thanks for the report. We are working on a fix ASAP and will post updates on https://github.com/dotcloud/docker/issues/3683.
Post reply on HN